all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 26650@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#26650: 26.0.50; Protect *Backtrace* from accidental killing
Date: Wed, 26 Apr 2017 14:03:36 +0300	[thread overview]
Message-ID: <83wpa7o2gn.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1704261930350.22037@calancha-pc> (message from Tino Calancha on Wed, 26 Apr 2017 19:36:54 +0900 (JST))

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Wed, 26 Apr 2017 19:36:54 +0900 (JST)
> cc: npostavs@users.sourceforge.net, Tino Calancha <tino.calancha@gmail.com>, 
>     26650@debbugs.gnu.org
> 
> >> +  (add-hook 'kill-buffer-hook
> >> +            (lambda () (if (> (recursion-depth) 0) (top-level))) nil t)
> >
> > This will throw to top-level when _any_ buffer is killed, as long as
> > we are in recursive-edit, no?
> No, because `add-hook' is called with non-nil LOCAL arg.

Right, sorry for not paying attention.





  reply	other threads:[~2017-04-26 11:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 12:02 bug#26650: 26.0.50; Protect *Backtrace* from accidental killing Tino Calancha
2017-04-25 12:13 ` npostavs
2017-04-25 12:18   ` Tino Calancha
2017-04-25 12:50     ` npostavs
2017-04-25 13:02       ` Tino Calancha
2017-04-26 10:07       ` Eli Zaretskii
2017-04-26 10:36         ` Tino Calancha
2017-04-26 11:03           ` Eli Zaretskii [this message]
2017-04-26 12:52             ` npostavs
2017-04-26 13:57               ` Tino Calancha
2017-04-26 15:33               ` Eli Zaretskii
2017-05-24  0:18                 ` npostavs
2017-04-26 10:49         ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wpa7o2gn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26650@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    --cc=tino.calancha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.