From: Lowell Gilbert <lgusenet@be-well.ilk.org>
Subject: Re: get rid of leftover auto save #files#
Date: Thu, 22 Apr 2004 17:57:10 GMT [thread overview]
Message-ID: <44vfjrdhft.fsf@be-well.ilk.org> (raw)
In-Reply-To: mailman.971.1082642525.1061.help-gnu-emacs@gnu.org
Kevin Dziulko <weaselboy1976@yahoo.com> writes:
> When I decide to abandon changes made to a buffer. I exit emacs without saving the file. It asks "Modified buffers exist; exit anyway?" I answer yes. Now I have an auto save #file# file there. How can I not get these files in this scenario? I want to keep auto save on because of it's many benefits.
I usually mark the file as unmodified before killing it.
[M-~ in the default configuration]
I suppose you could use the kill-buffer-hook or some related hook to
do this automatically...
next parent reply other threads:[~2004-04-22 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.971.1082642525.1061.help-gnu-emacs@gnu.org>
2004-04-22 17:57 ` Lowell Gilbert [this message]
2004-04-22 20:53 ` get rid of leftover auto save #files# Roodwriter
2004-04-23 15:42 ` Kevin Rodgers
2004-04-24 14:51 ` Lowell Gilbert
2004-04-26 17:31 ` Kevin Rodgers
2004-04-22 14:00 Kevin Dziulko
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=44vfjrdhft.fsf@be-well.ilk.org \
--to=lgusenet@be-well.ilk.org \
/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.
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).