all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: rrt@sc3d.org, 5552-done@debbugs.gnu.org
Subject: bug#5552: 23.1; desktop seems not quite to understand session management
Date: Sun, 02 May 2010 20:50:14 +0200	[thread overview]
Message-ID: <4BDDC966.9070905@swipnet.se> (raw)
In-Reply-To: <87eiktqvl4.fsf@stupidchicken.com>

2010-02-10 10:38, Chong Yidong skrev:
> Jan Djärv<jan.h.d@swipnet.se>  writes:
>
>> When you log out, the X connection is closed and emacs exits.
>> However, it does not run kill-emacs-hooks.  Desktop.el depends on that
>> hook to clean up after itself.
>>
>> Should we run kill-emacs instead of shut_down_emacs when exiting due
>> to X connection lost?
>
> 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.

kill-emacs is now run in Emacs 24 when X connection is lost, when SIGTERM or 
SIGHUP is received (Gnome session management uses SIGHUP to kill X clients).

	Jan D.







      parent reply	other threads:[~2010-05-02 18:50 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
2010-03-30 10:36     ` Re:Next pretest Jan D.
2010-05-02 18:50     ` Jan Djärv [this message]

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=4BDDC966.9070905@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=5552-done@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --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.