Clojurians Log v2

If anyone else is having issues with the debugger with VS Code 1.54 please chime in on this issue with details like OS and project type: https://github.com/BetterThanTomorrow/calva/issues/1055. I cannot reproduce the issues on Manjaro Linux or Windows 10 Pro.

Hi all, any ideas on how to get calva to auto generate the correct namespace? I am using the re-frame template out of the box and I only get the namespace of new files to be the name of the file. I went through the readme and I can’t see what I am missing.

With auto-generate namespace you mean when you crate a new file and the namespace added to that file?

@pez yes exactly

I only get (ns my-file) instead of (ns com.me.myfile)

I’m jacked in, and I have the correct source-path as generated in the re-frame template. I’ve tried also adding source-path to a few other places in the config map, but nothing has worked so far

I think it is broken. Please file as a bug.

@brandon.ringe we should let lsp do this, right?

Will do thank you

@pez I think that would be best going forward

Need help testing a VSIX again, dear Calva friends. I’ve added a command for evaluating the code from start of the list up to the cursor. Sounds simple enough, which it is. But I had to restructure the select-for-evaluation code a bit because gnomes and kittens where in the line of fire. So now I could have broken something. My testing indicates I haven’t, but it is late here in the North… • Here’s the PR with some details: https://github.com/BetterThanTomorrow/calva/pull/1061 • Here’s the VSIX: https://11931-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.178-1057-evaluate-to-point-b54846a6.vsix

@email113 ^