Clojurians Log v2
Clojure programming
Channels
Apps
calva
kiemdoder 2025-09-18T06:12:58.179539Z
I instrumented a function with ctrl+alt+c i and added a #break for a breakpoint as well. When I invoke the function the debugger stops at the first line of the function as expected but the breakpoint is ignored when I try to continue to the next breakpoint in the debugger. Are there limitations for where a #break can be added to the code?
kiemdoder 2025-09-18T06:16:21.901339Z
I played around and got the breakpoint to work by surrounding it with two statements.
(do)
#break
(do)
pez 2025-09-18T06:41:06.608609Z
Interesting workaround, how did you come up with that? 😃 I’m not really in the know about how this is supposed to work. It’s on the cider-nrepl level, I think, because Calva doesn’t manipulate the forms as they are being instrumented. You could try with using latest cider-nrepl and see if the problem is still there (it probably is, I don’t think the CIDER debugger has been updated much lately). If you are using Jack-in, there are settings in Calva for jack-in dependency versions. The places to find people who knows about the debugger is #nrepl and #dev-tooling.
kiemdoder 2025-09-18T06:44:04.591699Z
Thank you, I will have a look in those channels. Maybe someone's asked the question before.
kiemdoder 2025-09-18T06:48:04.715319Z
> Interesting workaround, how did you come up with that? The breakpoint was on the first line of a function body so I thought maybe it can't be on the first line of the body and surrounded it with the do's
🤘 1