GNU bug report logs - #26650
26.0.50; Protect *Backtrace* from accidental killing

Previous Next

Full log

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

From: Tino Calancha <tino.calancha <at> gmail.com>
To: npostavs <at> users.sourceforge.net
Cc: 26650 <at> debbugs.gnu.org, Tino Calancha <tino.calancha <at> gmail.com>
Subject: Re: bug#26650: 26.0.50; Protect *Backtrace* from accidental
 killing
Date: Tue, 25 Apr 2017 22:02:20 +0900 (JST)

On Tue, 25 Apr 2017, npostavs <at> users.sourceforge.net wrote:

> tags 26650 patch
> quit
>
> Tino Calancha <tino.calancha <at> gmail.com> writes:
>
>>>
>>> That's because you're still in the recursive edit, it's like evaluating
>>> '(error "hi")' before hitting 'q' in the *Backtrace* buffer.  You can
>>> use C-M-c (exit-recursive-edit) to get back to normal.  I think it would
>>> make sense to do that automatically if you kill the *Backtrace* buffer.
>> Yes, it would be useful.  I don't know how, though.
>> Sometimes i kill *Bactrace* from *Ibuffer*/*Buffer List* with the
>> recursive edit still ongoing.  It's a classical mistake.
>
> Actually, the obvious way of adding `top-level' (that's what 'q' does)
> to `kill-buffer-hook' does protect *Backtrace* from killing.
Good!  It solves the issue.

Previous Next

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