From: David Kastrup <dak@gnu.org>
Cc: belanger@truman.edu, emacs-devel@gnu.org
Subject: Re: Creating an empty file
Date: Wed, 24 Jan 2007 00:56:03 +0100 [thread overview]
Message-ID: <853b619u24.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87r6tlpqwi.fsf@lrde.org> (Michaël Cadilhac's message of "Tue\, 23 Jan 2007 18\:57\:33 +0100")
michael@cadilhac.name (Michaël Cadilhac) writes:
> Jay Belanger <belanger@truman.edu> writes:
>
>> David Kastrup <dak@gnu.org> writes:
>> ...
>>> This would probably also apply for an existing file that has been
>>> changed on disk, but not in the Emacs buffer. In this case it might
>>> possibly make sense to ask the "revert buffer" question before saving.
>>> In the case of a non-existing file, there is nothing to revert to,
>>> however.
>>
>> So are you suggesting that when saving a file whose buffer has not
>> been changed, that Emacs should compare it to the disk file anyhow?
>> I had always (always=for the last 10 seconds) thought that it didn't
>> for efficiency reasons.
>
> Well, the modification flag has a certain use that should be
> preserved. What may be done is to add a var
> `new-files-are-already-modified'.
>
> Maybe the (untested) following could help?
I don't think this a good idea since it will also cause Emacs to
refuse deleting the buffer without confirmation, and it will cause
autosaving to occur.
I think the current behavior is perfectly fine with regard to setting
the modification flag (or rather not setting it). The problem rather
is that C-x C-s consults nothing except the modification flag before
deciding not to save at all, and not asking a question about it. And
the prefix flag is already used for a different purpose, so we can't
use that to signal "I really mean it".
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-01-23 23:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86bqkphiyj.fsf@lola.quinscape.zz>
[not found] ` <87odopr8ga.fsf@lrde.org>
2007-01-23 16:35 ` Creating an empty file Jay Belanger
2007-01-23 16:48 ` David Kastrup
2007-01-23 17:19 ` Jay Belanger
2007-01-23 17:23 ` David Kastrup
2007-01-23 17:57 ` Michaël Cadilhac
2007-01-23 23:56 ` David Kastrup [this message]
2007-01-24 1:19 ` Stefan Monnier
2007-01-24 7:12 ` martin rudalics
2007-01-24 2:58 ` Giorgos Keramidas
2007-01-25 9:06 ` Kevin Rodgers
2007-01-25 10:36 ` Romain Francoise
2007-01-25 19:39 ` Stefan Monnier
2007-01-25 21:44 ` Richard Stallman
2007-01-25 22:01 ` martin rudalics
2007-01-25 22:07 ` Alfred M. Szmidt
2007-01-25 22:14 ` Lennart Borgman (gmail)
2007-01-26 11:43 ` Richard Stallman
2007-01-25 22:14 ` Piet van Oostrum
2007-01-23 18:20 ` Michaël Cadilhac
2007-01-23 16:49 ` Leo
2007-01-23 17:11 ` David Kastrup
2007-01-23 21:57 ` Phil Jackson
2007-01-24 7:37 ` David Kastrup
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=853b619u24.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=belanger@truman.edu \
--cc=emacs-devel@gnu.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.
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).