[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: <filename> changed on disk; really edit the buffer?

From: Jonathan Goldblatt
Subject: Re: <filename> changed on disk; really edit the buffer?
Date: Mon, 19 Nov 2007 07:46:36 -0500

>>>>> "Richard" == Richard Stallman <address@hidden> writes:

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


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

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

I haven't used auto-save-visited-file-name.  But if I did the
motivation would be to have a hook run at the time of the
autosave.  From the documentation I would assume that the various
write file hooks would be run at the time of the auto-save, and
would try to use saving to the file as a kludge to make what I
wanted happen.  Maybe the solution is a new hook variable that
defaults to the current auto-save function.

While on the subject of possible improvements to auto-save, it
would also be nice to have a command to compare the auto-save
file to the official copy; of course I might just not have found
it yet.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]