I use custom REPL snippets for this (I run clojure.test directly, rather than via Calva/CIDER testing infrastructure).

oh clever, that makes sense

Not sure if it's the cause, but I just updated to this and clojure-lsp doesn't start any more - even when manually clicking "Start" via the menu.

Hm, I just needed to be patient; it kicked in after a minute or so, not sure why so slow.

I had a situation yesterday where I think Calva had borked the clojure-lsp download and I had to manually find Calva’s extension folder and remove it. Not the same as you had there, @U7PBP4UVA, but similar symptoms (just that it never stopped spinning). I’m figuring what to do about it, because I don’t know how to reproduce…

It might be a case of slow internet - my experience was that the icon never started spinning when I clicked "Start". I moved my attention elsewhere and when I came back to VSCode, everything was back to normal.

That’s a really good question! I think it should work with using the Calva REPL API from #Joyride and call the doc macro. It produces a pretty predictable output that you can parse and display the signature in a statusbar item.

(with-out-str (clojure.repl/doc +)) => "-------------------------\nclojure.core/+\n([] [x] [x y] [x y & more])\n  Returns the sum of nums. (+) returns 0. Does not auto-promote\n  longs, will throw on overflow. See also: +'\n"

There’s also the command Trigger Parameter hints that shows the signature as a tiny hover and highlights the current parameter. Default binding is shift+cmd+space on mac. Could be shift+ctrl+space on windows/linux.

We could add Calva API for extracting the signature info for a symbol too, without too much effort. Let me know if you want to do it. 😃

Thanks for the Trigger Parameter hint! I never found that because 1Password had overwritten that keyboard shortcut but getting rid of that for this!