* bug#13531: 24.2.92; Normally closed Emacs leaves autosave files
@ 2013-01-23 7:13 Michael Heerdegen
2019-08-15 7:37 ` Lars Ingebrigtsen
0 siblings, 1 reply; 2+ messages in thread
From: Michael Heerdegen @ 2013-01-23 7:13 UTC (permalink / raw)
To: 13531
Hi,
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.
Thanks,
Michael.
In GNU Emacs 24.2.92.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10)
of 2013-01-21 on drachen
Bzr revision: schwab@linux-m68k.org-20130120225947-57ekte112o7cw53w
Windowing system distributor `The X.Org Foundation', version 11.0.10707000
System Description: Debian GNU/Linux 7.0 (wheezy)
Configured using:
`configure '--prefix=/usr/local/built/''
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#13531: 24.2.92; Normally closed Emacs leaves autosave files
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
0 siblings, 0 replies; 2+ messages in thread
From: Lars Ingebrigtsen @ 2019-08-15 7:37 UTC (permalink / raw)
To: Michael Heerdegen; +Cc: 13531
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-08-15 7:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.