[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ask-user-about-supersession-threat called when autorevert mode is se
From: |
Klaus Zeitler |
Subject: |
Re: ask-user-about-supersession-threat called when autorevert mode is set |
Date: |
Thu, 11 Nov 2004 13:18:39 +0100 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (usg-unix-v) |
>>>>> "Richard" == Richard Stallman <address@hidden> writes:
Richard>
Richard> running revert-buffer
Richard> verify-visited-file-modtime: returning (file 1097662185,
buffer 1097662183)
Richard> insert-file-contents: entering
Richard> insert-file-contents: calling Qafter_insert_file_set_coding
Richard> set-buffer-modified-p: entering
Richard> lock_file: entering
Richard>
Richard> Does this mean that set-buffer-modified-p's argument is t? It
Richard> would have to be, for lock_file to be called, I think. But why
Richard> would that happen? When after-insert-file-set-coding is called,
Richard> the buffer should be unmodified, in the visit case (which this
Richard> must be). So the argument to set-buffer-modified-p should be
Richard> nil.
I took a closer look and you're right it's not caused by
(set-buffer-modified-p modified-p) at the end of after-insert-file-set-coding
because modified-p is nil in this case.
But after-insert-file-set-coding calls set-buffer-file-coding-system
and this in turn calls (set-buffer-modified-p t).
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: address@hidden |
------------------------------------------
---
Old age is the most unexpected of things that can happen to a man. -- Trotsky