Fork me on GitHub

Does command refresh all namespaces write output somewhere? Can’t find any information on whether it is ran successfully or not


I think it's in the output channel “Calva says”.


Thanks. Good to know. I hid the output tab a long time ago and forgot about it.


Dear Calva-friends. I got reminded about Zazzle and decided to put up some Calva merch there as well. See There is Joyride merch there as welll. If you buy something there and it is your first Zazzle purchase, please consider using my invite link: It will give me credits on Zazzle so that I can buy stuff. 😃

🎊 1

I’m constantly making changes and scrambling to rich comments to evaluate things. For web apps i make the change, update the router then go to the rich comments. 1. Is there a way to minimize the back and forth or a better way? 2. Do you keep rich comments in every namespace or in just one file?


I keep rich comments for the thing I am working on just below the top level form I am working on. When there is a Rich comment below the current top level form Calva's command Calva: Add Rich Comment , will jump there instead of creating a new one. It is not perfect, but the workflow gets something like: 1. Make changes 2. Add Rich comment ctrl+alt+r c 3. Test changes 4. Jump back to top level form with Cursor Undo cmd+u (often several times, depending)

👍 1

I have RCFs all over my codebase. Many functions have a small RCF below them with either a call to the function -- as a sanity check -- or various small fragments that I wrote and evaluated as I was building the function up. Sometimes I delete those RCFs, if they really add no value to maintenance, but often I end up leaving them in the codebase -- as much for "future me" as anybody else. While I'm developing code, I tend to start it all off in an RCF and build things up from there, eventually copying the finished functions above the RCF into "real" code. I rely on the REPL and evaluating forms all the time and I run tests inside my editor via the REPL as well (I have a hot key bound to a snippet that runs the tests associated with the current ns -- so when I'm editing, I can just hit a hot key and it finds and runs the tests in it, without needing to switch to the test ns). I might use f12 to go through a chain of definitions and alt+leftarrow to come back to where I started, while I'm thinking about the next steps with my code, but mostly I stay in a single file at a time when working on stuff.

👍 1
Daniel Jomphe20:06:25

Adding to what Sean wrote, for now here we don’t have unit tests in a separate file, but some of our rich comments under some top-level forms are “hyperfiddled”. So instead of being

 ... ; => expected)
they are
 ... := expected)
and each time we eval the file (we configured Calva to always eval the entire file when we save it but you’re not obliged to buy into this), those RCF tests are executed and their results are reported. It’s also possible to expose those rcf/tests as clojure.test fixtures. To learn more about this, check

metal 1
👍 1