This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-08
Channels
- # announcements (1)
- # babashka (18)
- # beginners (32)
- # calva (3)
- # chlorine-clover (4)
- # cider (14)
- # clj-commons (24)
- # clj-kondo (1)
- # clojure (34)
- # clojure-europe (4)
- # clojure-filipino (1)
- # clojure-uk (4)
- # clojuredesign-podcast (2)
- # clojurescript (6)
- # conjure (3)
- # core-async (2)
- # datahike (1)
- # datomic (3)
- # emacs (3)
- # esprit (20)
- # fulcro (4)
- # graalvm (11)
- # helix (13)
- # honeysql (4)
- # jobs (1)
- # lumo (1)
- # observability (4)
- # off-topic (11)
- # other-lisps (6)
- # pathom (6)
- # re-frame (13)
- # reagent (1)
- # reitit (1)
- # shadow-cljs (26)
- # web-security (2)
- # xtdb (10)
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?
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.
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?
Thanks
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.