Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2020-12-18

Channels

#conjure
<
2020-12-18
>
dharrigan17:12:27

I can't recall, but does conjure have the same ability to render the result of the eval, inline, just like with emacs?

Olical17:12:20

Nope, older versions did, but it's on my short term roadmap

👍 3
dharrigan17:12:32

yuuuuss pluuuase 🙂

nate17:12:27

oh cool! glad to hear it's coming back at some point

nate17:12:46

I did some mob programming using vscode and it has in-line output and I was envious

dharrigan17:12:06

I've just been playing with spacemacs, to see if I'm missing out on anything

dharrigan17:12:18

nope is the answer, apart from that nice inline eval.

rafaeldelboni16:12:53

I do miss this from the old version

Olical11:12:49

Me too 🙂 I'm thinking turned off by default but not too sure, so you can flip it on with or without the HUD. So you can have both, none or just one. But the defaults will stay as they are today? Thoughts? (with regards to inline virtual text eval results) The only thing I didn't like about it was zero syntax highlighting and it all has to fit on one line, which is what the HUD was designed to work around. I think each have their own place, => nil is nice, => {{{{{:a-huge-nested-map-going-off-screen is not so nice. For example.

Olical11:12:09

I was also planning on using virtual text for arg list documentation as you hovered on forms, so I'll need to design it to support eval results and arg lists. Or maybe I should echo arg lists so they appear at the bottom of the screen and virtual text is reserved for results. To the hammock!

dharrigan11:12:48

yes, virtual text for doc forms would be super awsome too

dharrigan17:12:42

you know, like this (+ 1 2) => 3

dharrigan17:12:55

where => 3 is shown as virtual text beside the form.

Olical11:12:49

Me too 🙂 I'm thinking turned off by default but not too sure, so you can flip it on with or without the HUD. So you can have both, none or just one. But the defaults will stay as they are today? Thoughts? (with regards to inline virtual text eval results) The only thing I didn't like about it was zero syntax highlighting and it all has to fit on one line, which is what the HUD was designed to work around. I think each have their own place, => nil is nice, => {{{{{:a-huge-nested-map-going-off-screen is not so nice. For example.