Clojurians Log v2
calva
sorry, I asked a question on a thread earlier and @brandon.ringe helped me a lot, I just wanted to follow up on the last question: is there any Clojure tooling which doesn't have this limitation? (of only being able to debug forms which were explicitly re-evaluated using the REPL)
@zimablue You may also be interested in flow-storm. There are a couple of links to info about it in this issue: https://github.com/BetterThanTomorrow/calva/issues/1119
It works a bit differently, though, and is not integrated with the editor. Well, it also probably wouldn't help with the issue you're talking about either. Even still, it may interest you. :man-shrugging:
thanks a lot for this, belatedly, very interesting
Looks great! The feature where the result of an eval is shown next to the code (as opposed to the REPL window) is recent? I tried Calva a few months ago and if I remember correctly it didn’t do that, but I might have missed it then
Possibly Cursive. It has a very strong debugger.
Thanks! It’s an old feature. Doesn’t happen in the REPL window, though, so you might have missed it if you were mainly trying things out there.
I wondered that, but it says that it uses cider/nrepl ("extensively") in the docs, so it seems that it would share any limitations.
It is also using other stuff. 😃 The debugger is implemented directly on the JVM. Check this out: https://www.youtube.com/watch?v=ql77RwhcCK0
Nice, I can’t understand how I missed it 😅 I’ll try calva again later today! I’m an emacs user so I probably won’t switch to vscode anytime soon, but I often recommend vscode+calva for new clojure programmers, so I’d rather know how to use it to help troubleshooting
@dromar56 Great! I can recommend trying out the Getting Started REPL, and if you like it, then recommend that to newcomers.
Hey, How do I turn off inline eval? I prefer just seeing the results in the REPL.
Hello guys, I am trying to start my project with calva and I am using the leiningen + Legacy Figwheel project type. I usually don't have problems with it. But recently it started behaving strangely and it doesn't want to connect to a cljs repl. After which if you attempt to evaluate anything on it, it just doesn't happen. Sometimes the problem gets fixed on its own. For example if I wait till tomorrow it may startup normaly
You can't turn that off.
That looks like a bug. Can you file an issue on Github about it? If you do it from VS Code’s Help menu some info about your setup will be attached.