@jlmr Ok, I got your point. Indeed, Atom does not have registers, but it's kinda easy to simulate the behavior you want by using the info on "Extending Chlorine" part of documentation: https://github.com/mauricioszabo/atom-chlorine/blob/master/docs/extending.md
You can define a new command to Atom that will save the current editor's selection (or block, top-block, there are commands that allow you to get these parts) to a simple JS variable. Then, you can issue a command to evaluate then
Something like this. This example is in JS, you can convert to coffee if your init script is in coffeescript.
@seancorfield, thanks! I already use comments as you describe them (good to know they have a name π). Was looking to take it one step further for fast iteration as @mauricio.szabo described. Will take a look at this solution as well!
Hey all, slowly easing in to Clojure and Chlorine. Couple of basic things (comment form is great, so thanks π) - reloading of files. I guess itβs hard to do on automatically on each edit, so... manual reloading it is?
Next up, Iβm starting to use doc-for-var more. Is there any way to get the output NOT inline? It might be obsessive but Iβm constantly clearing the inline results. Getting them in a separate buffer would be neat. Ideas?
There's support for auto-reload (with require or with the additional clojure.tools.namespace
library) on save. I don't recommend it, to be honest, because it can lead to some inconsistent states
Also, there's currently no way to avoid the inline results. I could add an option to it, so it would render only on the console tab
Thanks for the quick reply π The inline results are probably with thinking about, not sure what others think. But yeah... if itβs easy to allow an option to put it in the console Iβm all for trying that out π
Is that the only way to get that information? I might be missing other ways of getting it?
Today, it goes both to inline and the console tab, so you can just ignore the inline results π
Hah, I hadnβt noticed. Thanks π