Clojurians Log v2
cider
Looking at the error it's some missing parameter in the nREPL request. Unexpected middleware errors are exactly what you'd expect them to be - an internal error in cider-nrepl that shouldn't have happened in the first place.
For that particular error it seems to me you've connected to some older instance of cider-nrepl, as in the past the request param for eldoc was named symbol and now it's named sym (to avoid shadowing the symbol function in the middleware code. Newer versions of the middleware support both param names for backwards compatibility, but the latest CIDER uses sym everywhere, so it can't work with older middleware.
I hope that makes it clear.
Yes, that is very helpful indeed. I’ll check with the group as to what what versions of Cider middleware are being included when VSCode does it’s Jack-in. Apart from this error, Cider is working really well with the VSCode live share port forwarding of the REPL, so if you are remotely collaborating on code with VSCode and Calva you can use Emacs too (although code changes only show when the file is saved by Emacs of course)
I was exploring the cider debugger, and I have never used the "inspect" feature of the debugger (because the binding "p" is mis-interpreted by spacemacs as the paste command). What am I missing? What are other ways I could invoke it?
@p.kushwaha97 examples of using Cider Inspect https://practicalli.github.io/spacemacs/evaluating-clojure/inspect.html My favourite feature is just leaving the cider-inspect window open, then all evaluations go there, even when using the usual evaluation commands If using Spacemacs develop, then I just added more key bindings for the rest of the cider-inspect functions
This is amazing. I just updated and used inspector for the first time, thanks for making it happen and writing that nice guide!
1👍I have a new video coming out in the next day or two that uses the cider-inspect tool a lot too... but I think that page covers most of it statically.