From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: Chong Yidong <cyd@stupidchicken.com>, 5552@debbugs.gnu.org, rrt@sc3d.org
Subject: bug#5552: 23.1; desktop seems not quite to understand session management
Date: Mon, 15 Feb 2010 09:11:46 -0500 [thread overview]
Message-ID: <jwv8waubnfl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4B78FC33.1010701@swipnet.se> (Jan D.'s message of "Mon, 15 Feb 2010 08:48:03 +0100")
>> There was a related thread about this a year ago, regarding how Emacs
>> responds to SIGTERM by calling shut_down_emacs rather than kill-emacs:
>> http://lists.gnu.org/archive/html/emacs-devel/2009-01/msg00530.html
>> The thread did not have a clear conclusion, but I'm in favor of changing
>> things to run kill-emacs in such situations. But I think this is best
>> done after the release, unless someone can come up with a very
>> convincing argument otherwise.
> Then we need to add some parameter or other mean to tell functions in
> kill-emacs-hook that is it not OK to interact with the user. This is the
> case if the X server closes connection in case of a logout. Desktop.el
> might in some situations try to ask the user if a desktop file shall
> be used.
Or alternatively use a new hook instead (call it `emacs-exit-hook' maybe),
i.e. pass that parameter via the control flow rather than the data flow.
Stefan
next prev parent reply other threads:[~2010-02-15 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 17:42 bug#5552: 23.1; desktop seems not quite to understand session management rrt
2010-02-09 18:57 ` Jan Djärv
2010-02-10 9:08 ` Jan Djärv
2010-02-10 9:38 ` Chong Yidong
2010-02-15 7:48 ` Jan D.
2010-02-15 14:11 ` Stefan Monnier [this message]
2010-03-30 10:36 ` Re:Next pretest Jan D.
2010-05-02 18:50 ` bug#5552: 23.1; desktop seems not quite to understand session management Jan Djärv
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=jwv8waubnfl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=5552@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=jan.h.d@swipnet.se \
--cc=rrt@sc3d.org \
/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.