This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-22
Channels
- # aatree (2)
- # beginners (14)
- # boot (190)
- # cider (16)
- # cljs-dev (15)
- # cljsjs (6)
- # cljsrn (7)
- # clojure (101)
- # clojure-austin (26)
- # clojure-berlin (2)
- # clojure-estonia (4)
- # clojure-greece (53)
- # clojure-russia (46)
- # clojurescript (44)
- # core-async (12)
- # cursive (57)
- # data-science (49)
- # datomic (5)
- # emacs (8)
- # hoplon (92)
- # ldnclj (20)
- # lein-figwheel (22)
- # leiningen (4)
- # mount (37)
- # om (103)
- # onyx (26)
- # parinfer (70)
- # proton (6)
- # re-frame (32)
- # reagent (1)
- # yada (24)
When CIDER (0.10.2) pops up an exception for a compilation error, it seems to hide the Compiler's error message that shows the source file and line number where the error occurred. E.g. ..., compiling:(dev.clj:44:3)
Is there a way to get it back?
for that reason I normally connect to a repl instead of cider-jack-in
. I start the repl in the cli, and use cider-connect
.
Yes, there are ways to get at them, in the REPL or *e
.
But why doesn't CIDER's pop-up show the message?
@stuartsierra: repro steps, please
@bozhidar: OK, I'll see what I can do.
Is there a way to suppress the output of evaling a large value in the REPL? I’ve got (def huge-thing …)
and just want the var def’d. I don’t need to see the whole value in the REPL.
@cap10morgan: AFAIK, (def x 12)
will print #'user/x
in the REPL and not 12
.
@dorab: I think that used to be true, but either it changed (running CIDER 0.10.2) or I turned on some setting that now makes it do both.
@cap10morgan: I just verified that in my CIDER 0.10.2 it still works the original way. I run a pretty stock CIDER.
hmm...
I wonder why mine is printing out the value too.