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.

then exceptions that cider hides, are displayed in the repl

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

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

i have no idea

as a newbie I have to pick my battles

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

Sounds like you're overriding def somewhere.