From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Functions in kill-emacs-hook aren't run if emacs gets killed with SIGTERM Date: Wed, 21 Jan 2009 15:36:12 -0500 Message-ID: References: <87prihxeu5.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1232572863 8094 80.91.229.12 (21 Jan 2009 21:21:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 21 Jan 2009 21:21:03 +0000 (UTC) Cc: Tassilo Horn , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 21 22:22:15 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LPkWK-0002CQ-7o for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2009 22:21:56 +0100 Original-Received: from localhost ([127.0.0.1]:40096 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPkV2-0005Or-Vb for ged-emacs-devel@m.gmane.org; Wed, 21 Jan 2009 16:20:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPkST-0004Cl-NY for emacs-devel@gnu.org; Wed, 21 Jan 2009 16:17:57 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPkSR-0004Bk-Ci for emacs-devel@gnu.org; Wed, 21 Jan 2009 16:17:56 -0500 Original-Received: from [199.232.76.173] (port=44012 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPkSR-0004Bf-93 for emacs-devel@gnu.org; Wed, 21 Jan 2009 16:17:55 -0500 Original-Received: from hsiamail.ps-av.com ([207.138.179.125]:3504 helo=psavcns.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LPkSO-0005Pp-2b; Wed, 21 Jan 2009 16:17:52 -0500 Original-Received: from ceviche.home [64.213.79.190] by psavcns.com with ESMTP (SMTPD32-8.12) id A73D1A0F0100; Wed, 21 Jan 2009 14:36:13 -0600 Original-Received: by ceviche.home (Postfix, from userid 20848) id C34EEB400C; Wed, 21 Jan 2009 15:36:12 -0500 (EST) In-Reply-To: (Eli Zaretskii's message of "Wed, 21 Jan 2009 20:42:58 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ X-Greylist: delayed 2496 seconds by postgrey-1.27 at monty-python; Wed, 21 Jan 2009 16:17:51 EST X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:108052 Archived-At: > No. Fatal signals, such as SIGTERM, are caught by a signal handler, > which runs emacs.c:shut_down_emacs. `kill-emacs' in a nutshell runs > `kill-emacs-hook' and then also calls shut_down_emacs. It would probably make sense to run kill-emacs-hook when we receive SIGTERM, although it does imply a significant change (basically handling SIGTERM similarly to SIGUSRn). >> A related question: What does emacs --daemon do when it receives a >> SIGTERM and there are unsaved buffers? > Sorry, I don't know. Someone else will have to answer this. I think it just does autosaves and then exits. Stefan