Correct. I rely on builtin VS Code stuff where it works, Calva/LSP for additional static stuff, and Clover for the REPL and dynamic stuff (socket REPL).

We have socket REPLs in many of our processes, not just for local development. No nREPL anywhere.

I was using Conjure (for vim) before which uses nrepl but I don't think it leverages much functionality there. Especially with LSP a lot of the useful stuff (go to definition, documentation etc) is provided anyway.

Im not sure about CLJS though. Does clover have support for that over shadow-cljs? Perhaps it's not the right place to ask but thanks for confirming, it's nice to know that the two plugins play well with each other.

I don't do cljs. I did spend some time looking at tooling again, maybe a year ago, and used Figwheel Main with a Socket REPL, so I was mostly writing cljc files and eval'ing/testing those via Clover, and relying on hot reloading to test it as cljs in the browser....

That was a much nicer combo than the last time I worked with cljs back in 2013/2014 🙂

Do you know if cider-nrepl middleware is loaded in the repl running in docker that you’re connecting to?

If jack-in works, I suspect your other repl is missing some dependency.

There’s a command to copy the jack-in command to your clipboard, and you can paste it somewhere to see what dependencies you might be missing, or just run jack-in and look at the command in the terminal.

Oh I know this one! It’s because when you're jacked in, calva uses cider instead of lsp for those features. cider gets confused because the path to the file in your container is different from the path on your system

is there a reason that it switches from lsp to cider? is it more accurate or is that just “left over” from a time before a good LSP version? mhh now that I think about it, cider would give you the information on the stuff you already eval’d and if you are still working in the file only lsp would have better info, so that should get priority? otherwise cider could send you somewhere that doesn’t exist anymore in the files?

I think the reason there’s this hybrid approach is that sometimes cider-nrepl gives better info than LSP, but I think also @U0ETXRFEW wants Calva to use repl tooling as much as possible when a repl is connected, maybe in case for some reason clojure-lsp doesn’t run for someone. However, I think most people don’t have a problem running clojure-lsp these days. There is the option of adding a setting to always use clojure-lsp for features that currently use one or the other depending on different factors. I don’t know how @U0ETXRFEW would feel about adding a setting like that, though. Settings do increase complexity in code and in troubleshooting.

Weird thing is it used to work until my Calva version got upgraded :thinking_face:

Can you try with an older version and see if that works? Remember that if clojure-lsp is set to latest you will be running with latest there regardless of Calva version.

Not currently. Please file an issue about it.

Not really. You can file a feature request to make it visible, and maybe someone who sees it knows how to do it and choose to spend the time.

Added a github issue, which I presume is what you meant (let me know if not).

Yes, thanks!