[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: |
Richard Stallman |
Subject: |
Re: ask-user-about-supersession-threat called when autorevert mode is set |
Date: |
Sat, 06 Nov 2004 22:37:18 -0500 |
running revert-buffer
verify-visited-file-modtime: returning (file 1097662185, buffer 1097662183)
insert-file-contents: entering
insert-file-contents: calling Qafter_insert_file_set_coding
set-buffer-modified-p: entering
lock_file: entering
Does this mean that set-buffer-modified-p's argument is t? It would
have to be, for lock_file to be called, I think. But why would that
happen? When after-insert-file-set-coding is called, the buffer
should be unmodified, in the visit case (which this must be). So the
argument to set-buffer-modified-p should be nil.
Now, in some cases after-insert-file-set-coding modifies the buffer.
That would call lock_file, and would cause a bug of this sort.
Is that the case that is happening to you?
I think we need to prevent it from calling lock_file.
I think I can do that, but in order to do it right, I need
to know these answers.
- Re: ask-user-about-supersession-threat called when autorevert mode is set,
Richard Stallman <=