"cider-eval-buffer" cannot be configured to *not* send evaluation result to echo area

[behrica]

Expected behavior

Cider should allow to configure where to send the result of the last expression to, if a buffer/file gets evaluated

Actual behavior

Cider always sends the evaluation result of the last expression in a filer/buffer on "cider-load-file" to the echo area of Emacs.
In case this expression is large, emacs will crash/being unresponsive immediately.

Steps to reproduce the problem

1. Create a empty clj file
2. Add a last expression into the file which produces a complex, deep, map
3. evaluate the buffer with "cider-eval-buffer"
4. Cider will send the result of 2) to the echo area and crash

CIDER version information

latest

[vemv]

I'll tentatively close the issue, mostly because it's old, but also because it's not clear what the desired alternative would be.

Feel free to continue the discussion.

[behrica]

I think the problem is still present.
It is in my view one case in which "not being careful" what to "evaluate" with cider results in a crashing emacs.
I had it while debugging a clj file which is "ment" to run via "clj xxx.clj" from command line, it does side effects, and result of the last line can be ignored.
I am not sure neither, what could be an alternative behavior.
Maybe allow to ignore output or redirect to a file or similar.

Ideally a "default cider configuration" should never crash even on a evaluation which produces very large output.
But this is nearly impossible to achieve, so at least we should maybe have configuration options which allow to reduce this risk.

[vemv]

Thanks!

Possibly (but I'm not sure), cider-print-quota is not honored in the echo area, while I see it working in the repl as intended.

Assuming that's the case, it would be in the interest of safety to change the default behavior to use the repl as the output destination. Or at the very least, indeed, making things configurable.