Open the Command Palette (`Ctrl+Shift+P` / ⌘+Shift+P) and type lsp, and you should find among the commands listed just about everything that would help as far as debug logging. That looks like the LSP binary is missing, or your permissions are broken on the binary. So I'm not sure how much info would actually show up in any of the logging. First thing I would do is double-check that calva.clojureLspVersion is either unset or set to latest, nightly, or a correct valid version number. Then restart code or run Developer: Reload Window to download it again.

And verify a good network connection before ^. Could be Calva wiped the good version, tried to download new one, and failed, leaving you no binary to run.

Thank you! USe the palette is a good idea. clojure-lsp works just fine in other projects so it is this (huge) one that has issues…

You didn't say how the above suggestion worked, so I guessing that did not solve it? 😔 "Other projects" could actually come into play regarding the interrupted-download theory: Another window may have been actively overwriting the binary file at the same time your current project tried to start it up. In that case simply running Restart LSP Server (or something like that) from the Command Palette (once the other project has finished the download) should have you off and running.

I have tried again and now LSP worked fine (though it took quite a while to start). I see now that I can access its diagnostic log through the command palette, so I will use that the next time. Thanks!

You can append the comment to a new line (or new line_s_) below the evaluated form.

Nice! Thanks!

Stupid me. I should have searched that myself in VSCode keyboard shortcuts. 🙂

Haha. I’m glad you didn’t. Now more people discovered this feature.

I moved from Metosin to a big corporation. I use VSCode / Calva to analyse some AWS SageMaker results. Clojure REPL and Calva is really great for this. My team members were wondering how I did the analysis. Using Clojure and Calva! 🙂

My colleague showed me the other day how he develops SQL queries using Clojure. Granted, it’s a Clojure code base, but I started to think it could be a cool demo/example project. Using some sql libraries and just get a nicer syntax for the SQL, and drive it from the editor.

And I guess you have common short-cuts which I think I got from Sean Corfield. In which case:- Ctl-Alt-C C ;; evals form to comment next line up-arrow Ctl-J join comment to end of form

ctrl+j should be enough, right? Depends from where you evaluate the form, I guess.

Yep right @U0ETXRFEW I was thinking about when I added => to the comment ;; and then had to go up and Join lines....

You can always use #C03DPCLCV9N to give yourself a command that adds it as a comment on the same line, prepended with a =>.

We are using it as a library via ClojureScript. See: https://github.com/BetterThanTomorrow/calva/blob/dev/src/cljs-lib/src/calva/fmt/formatter.cljs

Warning, quite horrible code. It is among the first Clojure I ever wrote.

No worries. Thanks for the info.