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

Previous Next

Full log

View this message in rfc822 format

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: Juri Linkov <juri <at> linkov.net>
Cc: 55863 <at> debbugs.gnu.org, Lars Ingebrigtsen <larsi <at> gnus.org>, dick <dick.r.chiang <at> gmail.com>
Subject: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*
Date: Thu, 09 Jun 2022 12:17:38 -0700

Juri Linkov <juri <at> linkov.net> writes:

>> (let ((debug-on-error t))
>>   (error "No chads please."))
>>
>> Then type "q", "C-x C-b", and note the empty lurker *Backtrace*.
>>
>> Apparently I'm the only one irked by this recurring bugaboo.
>
> A better question is why *Backtrace* is erased?
> Often I accidentally quit the backtrace, then
> try to switch to the *Backtrace* buffer to check
> the backtrace again, but to no avail.

FWIW I agree with this: I'm often annoyed that the backtrace is removed.
What's the harm in leaving it there?

Previous Next

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