emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#12863: closed (auto-revert does not detect changes


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#12863: closed (auto-revert does not detect changes within 1s of a revert)
Date: Tue, 13 Nov 2012 01:52:02 +0000

Your message dated Mon, 12 Nov 2012 20:50:52 -0500
with message-id <address@hidden>
and subject line Re: bug#12863: Annoying bug in revert-buffer
has caused the debbugs.gnu.org bug report #12863,
regarding auto-revert does not detect changes within 1s of a revert
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
12863: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12863
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Annoying bug in revert-buffer Date: Sun, 11 Nov 2012 12:42:17 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
I use revert-buffer on several log buffers. There is one annoying bug.
Sometimes Emacs sees that the buffer has changed and reloads it. But
when it changes in the same second again, the buffer is not reloaded
and you do not see the changes. First I thought it was a Windows
quirk, but now I have seen the same behaviour on Linux. (I am looking
more at log buffers I suppose.)

Is this a known bug?

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof



--- End Message ---
--- Begin Message --- Subject: Re: bug#12863: Annoying bug in revert-buffer Date: Mon, 12 Nov 2012 20:50:52 -0500 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Version: 24.4

Paul Eggert wrote:

> On 11/12/2012 12:04 PM, Glenn Morris wrote:
>> I see this comment in verify-visited-file-modtime:
>> 
>> /* If both [times] exist, accept them if they are off by one second.  */
>
> I've had my eye on that code for some time, figuring that
> it must be bogus but not having the time to prove that it
> was bogus.  Since it's now known to cause problems, I removed it
> in trunk bzr 110875. 

Thanks, I checked using `touch' and verify-visited-file-modtime that it
fixes the issue for me.

So this will be fixed in the next (probably) release after 24.3, not in
24.3 as I originally said.


--- End Message ---

reply via email to

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