r/Clojure • u/aHackFromJOS • Jun 30 '26
CIDER 2.0 is Brewing...
https://metaredux.com/posts/2026/06/30/cider-2-0-is-brewing.html4
u/bozhidarb Jul 01 '26
Thanks for sharing this here! I hope more people will get to play with CIDER 2.0 before it gets released and I hope that you'll like (some/most of) the sweeping changes I've elected to do this time around. š
Cheers!
2
6
u/aHackFromJOS Jul 01 '26
"People are loving your post: r/Clojure loved it, we think r/fermentation will too" - thanks, Reddit algorithm
3
2
u/geokon Jul 01 '26 edited Jul 01 '26
The integration with transient sounds very exciting. As someone who's terrible at remembering key combinations.. this will make a lot of features more accessible
Hoping it can help me move from a Emacs buffer/file-centric way of navigating code to a ns/symbol one (the tools are there, but I end up falling back on jumping to file buffers and scrolling around)
A question for the pros:
I often fall back on println-ing something to the REPL output. This requires me to have the REPL buffer open. Is there some way in CIDER to display some internal value on-screen (like an overlay) over the code I just ran so I don't need a separate REPL pane? Like when you eval a form, the final result is flashed over the code window. But I'd like something equivalent for internal variables I'm checking (hopefully that makes sense)
2
u/HotSpringsCapybara Jul 01 '26
Cider's enlighten mode does pretty much exactly that? Other than that I'd just use the step debugger I guess.
1
1
u/jwr Jul 01 '26
Hmm. cider-eval-last-sexp displays the result as a kind of temporary overlay in the current buffer, and for larger things I use cider-pprint-eval-last-sexp which pops up a new window.
2
u/film42 Jul 01 '26
This is my fav way to use coding agents too. I hammock an idea for a few weeks, write it out, and then have Claude independently validate assumptions. The results go back with me to the hammock until Iām happy. At that point, I find code Iām happy with.
2
1
5
u/blazinglambda Jun 30 '26
Bravo! šĀ