Subject: Re: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*

From: Lars Ingebrigtsen <[email-masked]>
Date: Fri, 10 Jun 2022 11:27:15 +0200

dick <[email-masked]> writes:

>> FWIW I agree with this: I'm often annoyed that the backtrace is
>> removed.  What's the harm in leaving it there?
>
> Because inhibit-debugger silently won't let you have more than one
> active session.  This was as confusing to me as a edebug beginner as
> when gdb inexplicably flies past a breakpoint.

Removing the text from the *Backtrace* buffer (or not) doesn't affect
whether `inhibit-debugger' is bound or not.  The `q' from the buffer
exits the recursive edit, which makes `inhibit-debugger' go back to its
normal value.

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