Fork me on GitHub

I keep forgetting to change the defaults for this. 😄 Your question reminded me to do it for the next release.


made me chuckle


It’s time I learned some Clojure myself! 😄

parrot 20

Can Cider (or orchard?) detect if some result will result into an overly long line and do something about it?


Actual Problem: doing eval-print-result when the result is just a long long string (e.g. contents of a byte output stream) Emacs will freeze.


+1 I have this problem over and over again, the same when logging a lot of data on standard output.


Evaluating in the source code file always truncated output by default, so prudent to use that approach if you dont know what the result looks like, I used evaluation in the source code buffer when doing a web scraping project and avoided any Emacs lockups or slow-downs due to very long lines. Logging into a REPL buffer is always going to be messy. Given there are so many logging tools out there that are easy to add, I never had the need to do this. I dont think its a very effective practice, especially inside Emacs, as you are hitting one of the biggest limitations of Emacs.