unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: jonathangoldblatt@yahoo.com
Cc: stephan.lukits@FernUni-Hagen.de, rudalics@gmx.at,
	jonathangoldblatt@yahoo.com, emacs-devel@gnu.org
Subject: Re: <filename> changed on disk; really edit the buffer?
Date: Thu, 22 Nov 2007 11:21:45 -0500	[thread overview]
Message-ID: <E1IvEoD-00064Z-AJ@fencepost.gnu.org> (raw)
In-Reply-To: <18244.10942.933776.973734@tower.localdomain> (jonathangoldblatt@yahoo.com)

The idea makes sense.  The variables should be named
auto-save-functions, according to conventions since 15 years ago.

But it isn't quite straightforward, because the code in fileio.c uses
a static variable auto_saving which alters the behavior of
write-region.

We do theoretically have a problem with this now, since the call to
Fsleep_for could run a process filter or sentinel.  So it would be
good to change that mechanism.

  reply	other threads:[~2007-11-22 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fg7idt$2c1$1@tamarack.fernuni-hagen.de>
     [not found] ` <mailman.2766.1193775394.18990.bug-gnu-emacs@gnu.org>
     [not found]   ` <fga6u2$kav$1@tamarack.fernuni-hagen.de>
     [not found]     ` <mailman.2810.1193861188.18990.bug-gnu-emacs@gnu.org>
     [not found]       ` <fgq1js$sae$1@tamarack.fernuni-hagen.de>
     [not found]         ` <mailman.3057.1194380790.18990.bug-gnu-emacs@gnu.org>
     [not found]           ` <fgv8a9$2tq$1@tamarack.fernuni-hagen.de>
     [not found]             ` <mailman.3145.1194554809.18990.bug-gnu-emacs@gnu.org>
     [not found]               ` <fh9s10$461$1@tamarack.fernuni-hagen.de>
     [not found]                 ` <mailman.3374.1194901774.18990.bug-gnu-emacs@gnu.org>
     [not found]                   ` <fhbptp$qfk$1@tamarack.fernuni-hagen.de>
     [not found]                     ` <mailman.3422.1194947662.18990.bug-gnu-emacs@gnu.org>
     [not found]                       ` <fhbt7q$j4d$1@tamarack.fernuni-hagen.de>
     [not found]                         ` <4739B12F.7000400@gmx.at>
     [not found]                           ` <E1Itjli-000760-SD@fencepost.gnu.org>
     [not found]                             ` <18241.34220.668384.165761@tower.localdomain>
     [not found]                               ` <E1IuKHL-000080-4R@fencepost.gnu.org>
     [not found]                                 ` <18242.27013.59638.550831@tower.localdomain>
2007-11-21 12:03                                   ` <filename> changed on disk; really edit the buffer? Richard Stallman
2007-11-21 12:55                                     ` jonathangoldblatt
2007-11-22 16:21                                       ` Richard Stallman [this message]
2007-11-21 17:47                                     ` martin rudalics
2007-11-22  8:22                                       ` Richard Stallman

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=E1IvEoD-00064Z-AJ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jonathangoldblatt@yahoo.com \
    --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).