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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 55863 <at> debbugs.gnu.org, dick.r.chiang <at> gmail.com, juri <at> linkov.net
Subject: Re: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*
Date: Thu, 09 Jun 2022 21:57:50 +0300

> Cc: 55863 <at> debbugs.gnu.org, dick <dick.r.chiang <at> gmail.com>
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Thu, 09 Jun 2022 19:34:42 +0200
> 
> 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...

Even if the links don't work, the backtrace itself provides valuable
information (and fining the functions is trivial with M-. so we don't
really need the links).

Previous Next

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