From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.pretest.bugs,gmane.emacs.devel Subject: Re: Exit hooks not run at logout on w32 Date: Tue, 04 Jul 2006 09:13:50 +0100 Message-ID: <44AA233E.8080000@gnu.org> References: <44A005B7.2080904@student.lu.se> <44A03B61.8080501@student.lu.se> <44A2B99B.1020002@student.lu.se> <44A2F974.7040609@gnu.org> <44A31C19.5050000@student.lu.se> <44A3A2DE.4040507@gnu.org> <44A3E918.5000304@student.lu.se> <85lkrg3t3a.fsf@lola.goethe.zz> <44A3FCCD.4040203@student.lu.se> <7dbe73ed0606291440r15b9f5pd1c7f35344d79c42@mail.gmail.com> <44A4576F.7060004@student.lu.se> <44AA10EC.2080503@student.lu.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1152000909 7527 80.91.229.2 (4 Jul 2006 08:15:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 4 Jul 2006 08:15:09 +0000 (UTC) Cc: emacs-pretest-bug@gnu.org, Emacs Devel , Mathias Dahl Original-X-From: emacs-pretest-bug-bounces+gebp-emacs-pretest-bug=gmane.org@gnu.org Tue Jul 04 10:15:07 2006 Return-path: Envelope-to: gebp-emacs-pretest-bug@gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Fxg3g-0008Rv-3T for gebp-emacs-pretest-bug@gmane.org; Tue, 04 Jul 2006 10:15:00 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fxg3f-0004Zj-EP for gebp-emacs-pretest-bug@gmane.org; Tue, 04 Jul 2006 04:14:59 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fxg2p-0004CV-Qq for emacs-pretest-bug@gnu.org; Tue, 04 Jul 2006 04:14:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fxg2o-0004BH-Jg for emacs-pretest-bug@gnu.org; Tue, 04 Jul 2006 04:14:07 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fxg2o-0004Ax-7t; Tue, 04 Jul 2006 04:14:06 -0400 Original-Received: from [213.86.207.50] (helo=exchange.integrasp.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FxgGR-0004ZP-EF; Tue, 04 Jul 2006 04:28:11 -0400 Original-Received: from [192.168.111.61] (localhost [127.0.0.1]) by exchange.integrasp.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NMA81VHB; Tue, 4 Jul 2006 09:05:55 +0100 Original-Received: from 192.168.111.61 ([192.168.111.61] helo=[192.168.111.61]) by ASSP-nospam; 4 Jul 2006 09:05:55 +0100 User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) Original-To: Lennart Borgman In-Reply-To: <44AA10EC.2080503@student.lu.se> X-BeenThere: emacs-pretest-bug@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for CVS Emacs." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-pretest-bug-bounces+gebp-emacs-pretest-bug=gmane.org@gnu.org Errors-To: emacs-pretest-bug-bounces+gebp-emacs-pretest-bug=gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.pretest.bugs:12738 gmane.emacs.devel:56468 Archived-At: Lennart Borgman wrote: > Could the problem that users unsaved data are not saved on w32 in this > situation be put in FOR-RELEASE? I think it is a serious bug. The user has requested a shutdown of the system, without saving their data first. How is it a bug that Emacs respects their wishes? > I have already sent a patch for this, but I have got no response on > that. There is possibly disagreement on what to do, but something > should be done and I do believe that the correct fix should make Emacs > follow the guidelines on w32. Jason said he had read them. I asked for > a link to them, but I have not seen it yet. Instead I provided the > above snippet. Here are the guidelines I was referring to: http://windowssdk.msdn.microsoft.com/en-us/library/ms723653.aspx Applications that have unsaved data could save the data to a temporary location and restore it the next time the application starts, or simply respect the user's request to shut down the system even though it will cause data loss. http://windowssdk.msdn.microsoft.com/en-us/library/ms723654.aspx If your application receives a shutdown notification while it is in the middle of an operation that should not be aborted, such as burning media or making a backup, it should display a dialog box. Warn the user what might happen if the operation is interrupted and enable the user to choose whether to cancel or continue the shutdown. If the user would like to cancel the shutdown, the application should return FALSE for this message. ... Applications should respond to this message as quickly as possible, saving time-consuming cleanup operations for the processing of the *WM_ENDSESSION* message.