Clojurians Log v2

I think suitable enhanced completions got broken after a shadow-cljs changes...I wanted to have a look there but did not have time

If I have a function with a long docstring, and I type in the buffer (my-function then emacs shows me the first few lines of the docstring in the minibuffer, when what I really want to see is the arglist. I suppose the arglist is at the end of the minibuffer, but it is obscured. Shouldn't they be shown in the other order?

If there a way in cider to see the values of the local variables when examining a stack trace?

i don't believe stack traces have any such information to provide

you can use (ex-info "boom" {:values :of-interest}) and these should be shown in the stack trace

yes thats for stacktraces caused by my call to ex-info.

I thought it should work. Let me see

pitty that local variables are not available in stack traces.

I think what you're looking for is eldoc? https://docs.cider.mx/cider/config/eldoc.html

Hey everyone. In the piggieback docs, it says I can set :nrepl.middleware.print/print to nrepl.util.print/pr to force using cljs's pr. How exactly do I set that? Is that something I put into dir-locals?

Yes, I have eldoc-mode enabled already. The problem is that the text of the docstring preceeds the arglist.

@jimka.issy You're getting the docstring, because for some reason this var wasn't resolved to a function type. You should check *nrepl-messages* to see what types was assigned to it by nREPL/cider-nrepl.

See https://docs.cider.mx/cider/0.26/usage/pretty_printing.html

Thanks