Fork me on GitHub
#cider
<
2016-02-22
>
stuartsierra14:02:20

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?

roberto14:02:12

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.

roberto14:02:33

then exceptions that cider hides, are displayed in the repl

stuartsierra14:02:31

Yes, there are ways to get at them, in the REPL or *e.

stuartsierra14:02:44

But why doesn't CIDER's pop-up show the message?

roberto14:02:54

i have no idea

roberto14:02:19

as a newbie I have to pick my battles simple_smile

bozhidar18:02:02

@stuartsierra: repro steps, please simple_smile

stuartsierra18:02:14

@bozhidar: OK, I'll see what I can do.

cap10morgan21:02:06

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.

dorab21:02:46

@cap10morgan: AFAIK, (def x 12) will print #'user/x in the REPL and not 12.

cap10morgan21:02:35

@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.

dorab21:02:08

@cap10morgan: I just verified that in my CIDER 0.10.2 it still works the original way. I run a pretty stock CIDER.

cap10morgan22:02:13

I wonder why mine is printing out the value too.

malabarba23:02:41

Sounds like you're overriding def somewhere.