From: Ken Brown <kbrown@cornell.edu>
To: "Strozzi, David J." <strozzi2@llnl.gov>, Eli Zaretskii <eliz@gnu.org>
Cc: "23483@debbugs.gnu.org" <23483@debbugs.gnu.org>
Subject: bug#23483: 24.5; cygwin emacs w32 doesn not ask to save files when windows shuts down
Date: Fri, 13 May 2016 19:12:14 -0400 [thread overview]
Message-ID: <8f6dd645-859e-a03a-2e5c-3a119b453b0e@cornell.edu> (raw)
In-Reply-To: <B5B0B301BBD57E40B9BEBAEFFE1C3FCE011855E6CA@PRDEXMBX-01.the-lab.llnl.gov>
On 5/13/2016 4:02 PM, Strozzi, David J. wrote:
> Hmmm, this doesn't sound like a great fix. It's really a "failsafe", but not what Windows users expect. When you open the file again, how will you know that there's another auto-save file? Will emacs tell you? What if you open the file in another program? Or you're editing source code / script and then make / run it, nothing will tell you about the auto-saved file.
>
> Perhaps better is to have emacs simply abort a restart / shutdown and require the user to manually close emacs. If it doesn't behave like other windows programs (query user to save unsaved files), then we have to remember emacs is special. You could have a parameter for whether emacs aborts a windows shutdown, default to yes, and then users and consciously shut it off if they want.
I'm not convinced that this is better. But as an experiment, I decided
to see if I could make emacs do what you want by having a system
shutdown trigger 'save-buffers-kill-emacs' instead of 'kill-emacs'.
What happened was that Windows complained that emacs was preventing it
from shutting down, and it gave me the choice of shutting down anyway or
canceling the shutdown. I chose the latter, at which point I was faced
with a non-responsive emacs that had to be killed.
I don't have any further ideas.
Ken
next prev parent reply other threads:[~2016-05-13 23:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 13:33 bug#23483: 24.5; cygwin emacs w32 doesn not ask to save files when windows shuts down Strozzi, David J.
2016-05-08 18:40 ` Eli Zaretskii
2016-05-10 15:16 ` Ken Brown
2016-05-10 16:32 ` Eli Zaretskii
2016-05-12 13:57 ` Ken Brown
2016-05-12 16:56 ` Eli Zaretskii
2016-05-12 19:58 ` Ken Brown
2016-05-13 16:22 ` Strozzi, David J.
2016-05-13 17:46 ` Eli Zaretskii
2016-05-13 18:05 ` Ken Brown
2016-05-13 20:02 ` Strozzi, David J.
2016-05-13 23:12 ` Ken Brown [this message]
2016-05-14 7:56 ` Eli Zaretskii
2016-05-14 7:22 ` Eli Zaretskii
2016-05-14 20:02 ` Strozzi, David J.
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=8f6dd645-859e-a03a-2e5c-3a119b453b0e@cornell.edu \
--to=kbrown@cornell.edu \
--cc=23483@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=strozzi2@llnl.gov \
/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).