unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 13531@debbugs.gnu.org
Subject: bug#13531: 24.2.92; Normally closed Emacs leaves autosave files
Date: Thu, 15 Aug 2019 00:37:12 -0700	[thread overview]
Message-ID: <87v9uyx4k7.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87r4lcv0ca.fsf@web.de> (Michael Heerdegen's message of "Wed, 23 Jan 2013 08:13:09 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> I mean this behavior:
>
> 0.  Start emacs -Q
> 1.  Find any file that is writable for you
> 2.  Make some change
> 3.  You've changed your mind.  You type C-x C-c.
>     Type n to negate the "Save file ..." question
>     Type "yes" to answer the "Modified buffers exist; exit anyway?"
>     question
>
> As a result, Emacs exits, but it leaves an autosave file.  IMHO this
> shouldn't be the case, because the user decidedly wanted to discard his
> changes.  Autosave files should only survive a session if Emacs crashed.
>
> With the current behavior, we only confuse users because they will think
> that the autosave files come from a crash, and will want to check if
> they have to recover anything.

It is perhaps somewhat confusing to auto-save files in this way
(especially after the user has answered "no" to the "save file..."
question), but I think on the whole that this behaviour is safer than
just discarding the contents.  Because we all answer stuff wrong once in
a while, and not saving something you wanted to save after all is a
bigger catastrophe than auto-saving a bit too much.

So I don't think not auto-saving will be too popular, and I'm closing
this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-08-15  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23  7:13 bug#13531: 24.2.92; Normally closed Emacs leaves autosave files Michael Heerdegen
2019-08-15  7:37 ` Lars Ingebrigtsen [this message]

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=87v9uyx4k7.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=13531@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).