bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation

[Lars Ingebrigtsen]

Jean Louis <bugs@gnu.support> writes:

> Please see the attached picture. I have turned off debug on error
> before evaluating (jnjn) non-existing function.

The picture (sent in a separate email) showed a backtrace, so you do
have debug-on-error switched on -- perhaps via
eval-expression-debug-on-error?  (It's a separate setting when you do
M-:, which is rather confusing.)

And if you hit `q' in the backtrace window, you run `top-level':

(defun debugger-quit ()
  "Quit debugging and return to the top level."
  (interactive)
  (if (= (recursion-depth) 0)
      (quit-window)
    (top-level)))


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no