Clojurians Log v2
cursive
@alex-eberts Just to check, are you using http://Deps.co as your repository, or is this just a standard deps.edn project?
I’m not using http://deps.co. It’s a standard deps.edn project.
Ok, sadly that means I can’t foist this off on @danielcompton 🙂.
Which version of Cursive are you using? Do you have custom repos in your deps file?
hi @cfleming I’m running Cursive 1.9.4-2020.3 at the moment but there’s nothing blocking me from upgrading to the newest version of Cursive if necessary.
has anyone got breakpoints working with the latest Cursive ?
working for me on IJ Ultimate 2020.3, Cursive 1.10.2-2020.3
I tried that (select-all, send to REPL) many times in different ways and it didn't work for me. Then I tried doing (use :reload this-namespace) in my (comment) block in the same file and it worked!
Select all and send is not the same thing, you want to use Tools -> REPL -> Load file in REPL which uses load-file and correctly creates the line numbers in the bytecode. Or require :reload will work too, anything that causes the whole namespace to be loaded using load-file.
got it. It works
thanks for your help!
I'm on the same versions except IJ CE
ok I've got it. Breakpoints don't work in a namespace if you eval code in that ns using "send form to REPL"
you have to eval code from another namespace because otherwise it can't find the information needed and the breakpoint turns into a grayed-out icon
so it looks like breakpoints are limited to code outside the namespace from which you're evaluating code
No, that’s not right - the main problem is generally line numbers in the generated code, which can change if you’re editing and sending only parts of a namespace (i.e. with send form).
If you’re debugging a namespace, I always recommend re-sending the whole file to ensure all the line numbers are correct.