From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-pretest-bug@gnu.org, Emacs Devel <emacs-devel@gnu.org>,
Mathias Dahl <mathias.dahl@gmail.com>
Subject: Re: Exit hooks not run at logout on w32
Date: Tue, 04 Jul 2006 09:13:50 +0100 [thread overview]
Message-ID: <44AA233E.8080000@gnu.org> (raw)
In-Reply-To: <44AA10EC.2080503@student.lu.se>
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.
next prev parent reply other threads:[~2006-07-04 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44A005B7.2080904@student.lu.se>
[not found] ` <44A01733.4010600@gnu.org>
[not found] ` <44A03B61.8080501@student.lu.se>
[not found] ` <ufyhrva9u.fsf@jasonrumney.net>
[not found] ` <44A2B99B.1020002@student.lu.se>
[not found] ` <44A2F974.7040609@gnu.org>
[not found] ` <44A31C19.5050000@student.lu.se>
[not found] ` <44A3A2DE.4040507@gnu.org>
2006-06-29 14:52 ` Exit hooks not run at logout on w32 Lennart Borgman
2006-06-29 15:00 ` David Kastrup
2006-06-29 16:16 ` Lennart Borgman
2006-06-29 21:40 ` Mathias Dahl
2006-06-29 22:42 ` Lennart Borgman
2006-07-04 6:55 ` Lennart Borgman
2006-07-04 8:13 ` Jason Rumney [this message]
2006-07-05 15:36 ` Stuart D. Herring
2006-07-04 8:36 ` Mathias Dahl
2006-07-04 8:49 ` Jason Rumney
2006-07-04 16:49 ` Lennart Borgman
2006-07-04 9:24 ` Kim F. Storm
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44AA233E.8080000@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=mathias.dahl@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).