Clojurians Log v2
chlorine-clover 2020-01-04
@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?
I'd strongly encourage getting into a workflow where you edit, eval block, edit, eval block, sprinkled with eval'ing test forms, so your feedback loop is super tight -- and you don't need to save files (or reload them) while you are iterating on small changes. I often work for five, ten minutes without saving, but I eval every single edit I make, and I eval test forms (in RCFs) regularly to validate my changes. I only save files when I'm "done" which each small group of changes.
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 😁
I love having the docstrings render inline. I keep the console minimized to just a few lines at the bottom of my screen while working and only use it to look at exception details if my code does something "bad".
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 👍
@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.