From: Glenn Morris <rgm@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 21833@debbugs.gnu.org, Stelian Iancu <si@siancu.net>
Subject: bug#21833: 24.4; desktop-kill, which is interactive, is in kill-emacs-hook
Date: Thu, 12 Nov 2015 18:38:48 -0500 [thread overview]
Message-ID: <do1tbudbzr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAGbimxbMh7-bdM2pPDBsOx8Qz61g=2ZE5PFTun-P+Q6+fj0=uw@mail.gmail.com>
The point is, kill-emacs-hook can run in situations where it is
impossible for Emacs to interact with the user.
Any yes-or-no-p questions will never be answered.
Emacs will hang and have to be forcibly killed.
Exactly as it says in the OP.
So don't put anything on kill-emacs-hook that needs an interactive
response from the user. Decide on a sensible non-interactive behaviour,
and for the interactive case use kill-emacs-query-functions.
The documentation seems clear to me.
next prev parent reply other threads:[~2015-11-12 23:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 22:43 bug#21833: 24.4; desktop-kill, which is interactive, is in kill-emacs-hook Michael Arntzenius
2015-11-12 20:07 ` Stelian Iancu
2015-11-12 20:11 ` Glenn Morris
2015-11-12 20:24 ` Stelian Iancu
2015-11-12 20:50 ` Eli Zaretskii
2015-11-12 21:38 ` Glenn Morris
2015-11-12 23:04 ` Juanma Barranquero
2015-11-12 23:38 ` Glenn Morris [this message]
2015-11-12 23:53 ` Juanma Barranquero
2015-11-13 0:27 ` Juanma Barranquero
2015-11-13 7:59 ` Eli Zaretskii
2015-11-13 9:39 ` Juanma Barranquero
2015-11-13 10:03 ` Eli Zaretskii
2015-11-13 10:17 ` Juanma Barranquero
2015-11-13 14:07 ` Eli Zaretskii
2015-11-13 14:36 ` Juanma Barranquero
2015-11-13 7:56 ` Eli Zaretskii
2015-11-13 9:30 ` Juanma Barranquero
2015-11-13 10:01 ` Eli Zaretskii
2015-11-13 10:14 ` Juanma Barranquero
2015-11-13 14:05 ` Eli Zaretskii
2015-11-13 14:35 ` Juanma Barranquero
2015-11-13 18:55 ` Eli Zaretskii
2015-11-15 11:54 ` Juanma Barranquero
2015-11-15 19:40 ` Eli Zaretskii
2015-11-13 8:36 ` Eli Zaretskii
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=do1tbudbzr.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=21833@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=si@siancu.net \
/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.