[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: martin rudalics
Subject: Re: <filename> changed on disk; really edit the buffer?
Date: Wed, 31 Oct 2007 19:34:07 +0100
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

> Hm.  I couldn't find this file attribute within the Windows Explorer.

I never use the Explorer, most file managers allow doing that easily.
You could also try a GNU port like touch.exe.

> Within dired I found the operation "Change Timestamp ... (T)".  I tried
> it but it didn't help.  Could you please be a bit more detailed about
> what I should do exactly.

Experiment with the functions in section 27.6 Buffer Modification Time
of the Elisp manual.  `verify-visited-file-modtime' is probably the one
causing the complaints, if it returns nil you get the message.
`clear-visited-file-modtime' (this should be done when you open a file)
and `set-visited-file-modtime' (usually done when you save a file)
should both assert that the message is not issued, hence if you do
either of these and afterwards get the message for that buffer,
something is wrong with Emacs' way of handling modification times.

Hence you can, for example, do



after opening a file that usually throws the messages and see what


(verify-visited-file-modtime (current-buffer))


reply via email to

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