Fork me on GitHub
Carsten Behring19:09:24

I have the impression that "cider-load-file" always prints the evaluation result of the last expression in a buffer into the echo area of emacs. If this is "large", emacs crashes for sure. I did not find a way to disable this. Is there one ?


I think there is a defcustom that controls this behavior: cider-use-overlays defaults to both which prints to the echo area and an overlay. If it's just set to t it doesn't print in the echo area. I think cider uses that for cider-load-file eventually.


Another solution is to put a nil at the end of the file being loaded.

Carsten Behring08:09:05

I tried to set "cider-use-overlays", but it does not change anything for "cider-load-file". It works for "cider-eval-sexp" and company

Carsten Behring08:09:58

It might be that this was never noted as a big problem. In most clojure files, the last expression is a function definition. We do data analysis in clojure using notespace and we have sometimes top level expressions which generate large vega specs. Typically they get rendered in browser via specific functions, but if I press by mistake "C-c C-l" on such a file, emacs dies directly.

Carsten Behring08:09:26

But only if the last expression by coincidence is a plot specification.....


Well, I thought cider-use-overlays might be it, I looked through some of the cider emacs lisp and didn't see any other defcustom vars that might be controlling that behavior.


cider-jack-in hangs and if I hit enter it shows me a nil> prompt.


How do you configure with nrepl cider uses? Mine is using 0.9.0-beta2 and the little [===] equals signs loading indicator just goes on and on, well after the messages buffer says [nREPL] server started on 50068