unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: martin rudalics <rudalics@gmx.at>, stephan.lukits@FernUni-Hagen.de
Cc: bug-gnu-emacs@gnu.org
Subject: Re: <filename> changed on disk; really edit the buffer?
Date: Sun, 18 Nov 2007 08:00:58 -0500	[thread overview]
Message-ID: <E1Itjli-000760-SD@fencepost.gnu.org> (raw)
In-Reply-To: <4739B12F.7000400@gmx.at> (message from martin rudalics on Tue, 13 Nov 2007 15:14:07 +0100)

    We could, in auto_save_1, do something like

    if (! NILP (Fstring_equal (current_buffer->filename,
			       current_buffer->auto_save_file_name)))
       Fclear_visited_file_modtime;

    if the Fwrite_region succeeds, but I'm not sure of any implications of
    this.  For example, current_buffer->save_length would not get set in
    Fwrite_region.

It would be easy enough to do those parts of the actions of
Fclear_visited_file_modtime which are right, and not the rest.

    Alternatively, we could try to simply save the buffer
    which is the behavior described in the Elisp manual but this might be
    more tricky.

Yes, it would be.

    Indeed.  Given the fact that apparently you are the first to report this
    bug it seems that the option `auto-save-visited-file-name' is hardly
    ever useful (at least nowadays).

It may not be very useful.  This option is historical since the
original Emacs.  I am sure some people used it in the 70s, but
maybe few people use it now.

      The most attractive solution would be
    to get rid of it.

Maybe we should do that, but before we do, we should ask the users
whether they mind.  Maybe some people have good reasons to use it.

Stephen, what was your motive for using it?




  reply	other threads:[~2007-11-18 13:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 15:26 <filename> changed on disk; really edit the buffer? Stephan Lukits
2007-10-30 20:16 ` Eli Zaretskii
2007-10-30 20:36 ` Jason Rumney
2007-10-30 22:15 ` martin rudalics
     [not found] ` <mailman.2766.1193775394.18990.bug-gnu-emacs@gnu.org>
2007-10-31 15:28   ` Stephan Lukits
2007-10-31 20:06     ` Eli Zaretskii
     [not found]     ` <mailman.2810.1193861188.18990.bug-gnu-emacs@gnu.org>
2007-11-06 15:36       ` Stephan Lukits
2007-11-06 20:26         ` Eli Zaretskii
2007-11-06 22:03         ` martin rudalics
     [not found]         ` <mailman.3057.1194380790.18990.bug-gnu-emacs@gnu.org>
2007-11-08 15:01           ` Stephan Lukits
2007-11-08 20:46             ` Eli Zaretskii
     [not found]             ` <mailman.3145.1194554809.18990.bug-gnu-emacs@gnu.org>
2007-11-12 15:39               ` Stephan Lukits
2007-11-12 21:09                 ` Eli Zaretskii
     [not found]                 ` <mailman.3374.1194901774.18990.bug-gnu-emacs@gnu.org>
2007-11-13  9:15                   ` Stephan Lukits
2007-11-13  9:18                     ` Jason Rumney
2007-11-13 11:34                       ` Lennart Borgman (gmail)
2007-11-13  9:51                     ` martin rudalics
     [not found]                     ` <mailman.3422.1194947662.18990.bug-gnu-emacs@gnu.org>
2007-11-13 10:12                       ` Stephan Lukits
2007-11-13 14:14                         ` martin rudalics
2007-11-18 13:00                           ` Richard Stallman [this message]
2007-11-19 12:46                             ` Jonathan Goldblatt
     [not found]                               ` <E1IuKHL-000080-4R@fencepost.gnu.org>
2007-11-20  4:58                                 ` jonathangoldblatt
     [not found]                           ` <mailman.3740.1195390867.18990.bug-gnu-emacs@gnu.org>
2007-11-20 15:36                             ` Stephan Lukits
2007-11-21 12:04                               ` Richard Stallman
     [not found]                               ` <mailman.3887.1195646697.18990.bug-gnu-emacs@gnu.org>
2007-11-21 20:15                                 ` Hallvard B Furuseth
     [not found]                       ` <mailman.3424.1194948672.18990.bug-gnu-emacs@gnu.org>
2007-11-18 19:12                         ` mdaily2002
2007-11-18 19:22                           ` mdaily2002
2007-11-19  9:13                             ` martin rudalics
     [not found]         ` <mailman.3060.1194386657.18990.bug-gnu-emacs@gnu.org>
2007-11-08 15:07           ` Stephan Lukits
2007-11-08 16:21             ` martin rudalics
     [not found] ` <mailman.2769.1193782517.18990.bug-gnu-emacs@gnu.org>
2007-10-31 15:58   ` Stephan Lukits
2007-10-31 18:34     ` martin rudalics
     [not found] ` <mailman.2770.1193784516.18990.bug-gnu-emacs@gnu.org>
2007-10-31 16:01   ` Stephan Lukits
     [not found] <mailman.2764.1193769505.18990.bug-gnu-emacs@gnu.org>
2007-11-01  2:28 ` Jim Dishaw
     [not found] ` <mailman.2828.1193900584.18990.bug-gnu-emacs@gnu.org>
2007-11-06 15:37   ` Stephan Lukits

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=E1Itjli-000760-SD@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=rudalics@gmx.at \
    --cc=stephan.lukits@FernUni-Hagen.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).