GNU bug report logs - #55863
29.0.50; [PATCH] Avoid hanging chad of *Backtrace*

Previous Next

Full log

Message #63 received at 55863 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: dick <dick.r.chiang <at> gmail.com>
Cc: Eric Abrahamsen <eric <at> ericabrahamsen.net>, 55863 <at> debbugs.gnu.org
Subject: Re: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*
Date: Fri, 10 Jun 2022 11:27:15 +0200

dick <dick.r.chiang <at> gmail.com> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.