From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>, "Strozzi, David J." <strozzi2@llnl.gov>
Cc: 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 14:05:22 -0400 [thread overview]
Message-ID: <9f6d64ef-03d3-d8d6-2afe-2465ee27dc91@cornell.edu> (raw)
In-Reply-To: <83inyh97g8.fsf@gnu.org>
On 5/13/2016 1:46 PM, Eli Zaretskii wrote:
>> From: "Strozzi, David J." <strozzi2@llnl.gov>
>> CC: "23483-done@debbugs.gnu.org" <23483-done@debbugs.gnu.org>
>> Date: Fri, 13 May 2016 16:22:43 +0000
>>
>> Thanks for addressing this! The usual behavior of windows programs on restart or shutdown is to ask the user to save unsaved files, rather than saving them silently. The current patch to save automatically is better than losing data, but prompting the user I think would be the best thing. Or even having emacs abort the shutdown and give a message like "emacs cancelled shutdown due to unsaved files."
>
> The patch doesn't save files automatically, it performs "auto-save",
> which saves the modified buffers into separate files, from which you
> can restore afterwards.
>
> FWIW, I don't see why asking the user would be better.
Agreed. I would just add that the next time you try to edit one of the
affected files, Emacs will warn you that there's an auto-save file and
will suggest that you consider running M-x recover-this-file.
Ken
next prev parent reply other threads:[~2016-05-13 18:05 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 [this message]
2016-05-13 20:02 ` Strozzi, David J.
2016-05-13 23:12 ` Ken Brown
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=9f6d64ef-03d3-d8d6-2afe-2465ee27dc91@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).