From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard M Stallman Newsgroups: gmane.emacs.devel Subject: Re: Functions in kill-emacs-hook aren't run if emacs gets killed with SIGTERM Date: Thu, 22 Jan 2009 20:52:42 -0500 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1232675679 882 80.91.229.12 (23 Jan 2009 01:54:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 23 Jan 2009 01:54:39 +0000 (UTC) Cc: eliz@gnu.org, emacs-devel@gnu.org, tassilo@member.fsf.org, monnier@iro.umontreal.ca To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 23 02:55:51 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 1LQBGp-0003gw-IN for ged-emacs-devel@m.gmane.org; Fri, 23 Jan 2009 02:55:43 +0100 Original-Received: from localhost ([127.0.0.1]:50437 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQBFX-0000TN-Ti for ged-emacs-devel@m.gmane.org; Thu, 22 Jan 2009 20:54:23 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQBFS-0000Sl-Bj for emacs-devel@gnu.org; Thu, 22 Jan 2009 20:54:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQBFP-0000Rw-TK for emacs-devel@gnu.org; Thu, 22 Jan 2009 20:54:16 -0500 Original-Received: from [199.232.76.173] (port=50967 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQBFP-0000Rt-MY for emacs-devel@gnu.org; Thu, 22 Jan 2009 20:54:15 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:48382) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQBFP-0000YJ-Dv; Thu, 22 Jan 2009 20:54:15 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1LQBDu-000677-SM; Thu, 22 Jan 2009 20:52:42 -0500 In-reply-to: (message from Andreas Schwab on Thu, 22 Jan 2009 11:08:32 +0100) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:108121 Archived-At: The main difference between SIGUSRx and SIGTERM is that SIGTERM is the normal way to stop a process, while SIGUSRx are meant for communication to it. So it seems to me that Emacs should pass SIGUSRx to Lisp code and otherwise ignore it. I believe that's what it did in the past. At some point it pushed an event which could run a command later.