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: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Juri Linkov <juri <at> linkov.net>
Cc: 55863 <at> debbugs.gnu.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 19:34:42 +0200

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

> 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.

I don't think you can usefully interact with it after exiting the
recursive edit?  That is, I think all the stuff that's bound in the
`debug' command (debugger-outer-match-data etc etc) has to continue to
be bound...

But perhaps that can be fixed?

-- 
(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.