From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: Functions in kill-emacs-hook aren't run if emacs gets killed with SIGTERM Date: Sat, 24 Jan 2009 12:40:50 +0800 Message-ID: <497A9BD2.4010607@gnu.org> References: <87prihxeu5.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1232772120 21427 80.91.229.12 (24 Jan 2009 04:42:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 24 Jan 2009 04:42:00 +0000 (UTC) Cc: tassilo@member.fsf.org, Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 24 05:43:13 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 1LQaMR-00084o-0K for ged-emacs-devel@m.gmane.org; Sat, 24 Jan 2009 05:43:11 +0100 Original-Received: from localhost ([127.0.0.1]:43717 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQaL9-00023o-H7 for ged-emacs-devel@m.gmane.org; Fri, 23 Jan 2009 23:41:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQaKi-0001oS-Rb for emacs-devel@gnu.org; Fri, 23 Jan 2009 23:41:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQaKg-0001nZ-Sn for emacs-devel@gnu.org; Fri, 23 Jan 2009 23:41:24 -0500 Original-Received: from [199.232.76.173] (port=50490 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQaKg-0001nT-L3 for emacs-devel@gnu.org; Fri, 23 Jan 2009 23:41:22 -0500 Original-Received: from rv-out-0708.google.com ([209.85.198.240]:36531) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQaKf-0000KG-FW; Fri, 23 Jan 2009 23:41:21 -0500 Original-Received: by rv-out-0708.google.com with SMTP id k29so5961486rvb.6 for ; Fri, 23 Jan 2009 20:41:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=92eVHtNKNA+OEuaJj402fL11Xjf95ZFwYb51UHUkD4s=; b=lKmSV1tt8hFol0heon4hFpVg82WMda5jyaxB+riXnmqZdR0t94/b5xGetzIJDSXF4b Lci2mMm6zkE1JBkVC7N9fbtKnOzYKcENHfE6rUAlHAUEsoohfZ44lv1zdx5A0rYJxAQJ erJQ/O/VU0z8omYSU20noKu2cjVfWn1PzbuW8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=loECYAqlPx3UiliGucZWwh/fbXN5ySTDOF38GKluIuJMzyM1ON/ipwl2eT69yNQfbF w7lgzuXjRsTdYwXpsbM96Th/1+F4owMkYJpokRBlRZgj+lsdPOf8tqt+ly6l0FOe57wU p/gKXZ69YLqaQUbDk8D6Sq5HG6ONfxEh1Ga34= Original-Received: by 10.143.31.4 with SMTP id i4mr661950wfj.102.1232772080238; Fri, 23 Jan 2009 20:41:20 -0800 (PST) Original-Received: from ?192.168.249.26? ([118.101.26.137]) by mx.google.com with ESMTPS id 30sm17175766wfg.5.2009.01.23.20.41.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 23 Jan 2009 20:41:19 -0800 (PST) User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:108177 Archived-At: Eli Zaretskii wrote: > On balance, I would leave things as they are, i.e. don't run > kill-emacs-hook when we get SIGTERM. After all, we are being killed, > so only the minimum necessary cleanup should be in order. > Another case for not running kill-emacs-hook for SIGTERM is that some elisp packages seem to get themselves into inconsistent states (semantic is terrible for this) where they throw errors from kill-emacs-hook, so the user is forced to kill emacs using SIGTERM. Changing SIGTERM to also run kill-emacs-hook would mean only SIGKILL can kill emacs in these circumstances.