This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-27
Channels
- # beginners (113)
- # calva (39)
- # cider (18)
- # cljs-dev (19)
- # cljsrn (1)
- # clojure (80)
- # clojure-dusseldorf (1)
- # clojure-finland (1)
- # clojure-gamedev (1)
- # clojure-germany (2)
- # clojure-italy (38)
- # clojure-nl (16)
- # clojure-spec (90)
- # clojure-uk (81)
- # clojurescript (28)
- # clojutre (9)
- # cursive (47)
- # data-science (4)
- # datomic (21)
- # emacs (1)
- # events (2)
- # fulcro (11)
- # graphql (2)
- # hoplon (8)
- # hyperfiddle (23)
- # jobs (2)
- # kaocha (4)
- # lein-figwheel (1)
- # luminus (1)
- # mount (1)
- # off-topic (41)
- # pathom (5)
- # pedestal (27)
- # reitit (6)
- # remote-jobs (7)
- # ring-swagger (6)
- # shadow-cljs (42)
- # spacemacs (1)
- # sql (9)
- # tools-deps (6)
- # uncomplicate (2)
- # vim (5)
clojure.pprint/pprint
prints those values very differently. I understand CIDER is using a different pretty-printer now (not sure which one?). But it seems very strange for any pretty printer to print maps and strings indistinguishably.
can you verify that this doesn't happen for you if you (setq cider-repl-use-pretty-printing nil)
hello! trying to debug an error in my tests in cider-nrepl
the message I receive is significant, but unfortunately I do not see the stacktace
it is of course wrapped in an nrepl message so I wonder if there is a way to attach the stacktrace of errors as well?
I see
Message: {:id 2, :msg "clojure.lang.Symbol cannot be cast to clojure.lang.Namespace", :session "fa2fd41b-7660-472e-874c-a7c6eebf6254", :status ["notification"], :type "error"}
(new to nrepl debugging 😄)
ok I might have found a hack
(catch Exception e
(let [stack-str (clojure.string/join "\n" (.getStackTrace e))]
(notify-client @debugger-message stack-str #_ (.getMessage e) :error))
false)
my problem specifically is in cider.nrepl.middleware.debug