You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Evaluate the expression with cider-eval-last-sexp (C-x C-e). Wait a few seconds, and abort with cider-interrupt (C-c C-b). Emacs will not crash.
On the other hand, if you use cider-pprint-eval-last-sexp (C-c C-p), the cider-result buffer will start filling with evaluation results. Cider-interrupt appears to halt evaluation, but doesn't prevent cider-eval-last-sexp from printing. Finally, killing the cider-result buffer will prevent Emacs from crashing, but cider-pprint-eval-last-sexp will no longer print future evaluations to cider-result.
The text was updated successfully, but these errors were encountered:
Hmm, that's nasty. Not sure what the best way to handle this would be. After all - printing infinite sequences is bound to be problematic. let binding print-length seems like the best idea to me, but that'll look kind of ugly in the Emacs Lisp code. A pretty printing middleware seems like a good alternative.
First, do something that won't terminate:
Evaluate the expression with cider-eval-last-sexp (C-x C-e). Wait a few seconds, and abort with cider-interrupt (C-c C-b). Emacs will not crash.
On the other hand, if you use cider-pprint-eval-last-sexp (C-c C-p), the cider-result buffer will start filling with evaluation results. Cider-interrupt appears to halt evaluation, but doesn't prevent cider-eval-last-sexp from printing. Finally, killing the cider-result buffer will prevent Emacs from crashing, but cider-pprint-eval-last-sexp will no longer print future evaluations to cider-result.
The text was updated successfully, but these errors were encountered: