GNU bug report logs -
#20943
25.0.50; Dired buffers are not always auto-reverterd
Previous Next
Reported by: Mark Karpov <markkarpov <at> openmailbox.org>
Date: Tue, 30 Jun 2015 18:24:02 UTC
Severity: normal
Found in version 25.0.50
Done: Mark Karpov <markkarpov <at> openmailbox.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
When I manually evaluate ‘dired-buffer-stale-p’ (in «frozen» buffer) it
returns t, this function works OK. The problem is that control flow
doesn't reach second portion of messages when ‘auto-revert-handler’ is
called for Dired buffer in question. I think problem is here:
(when (or auto-revert-tail-mode (not (buffer-modified-p)))
...)
(or auto-revert-tail-mode (not (buffer-modified-p))) is obviously nil
when it shouldn't be nil. I don't know what ‘auto-revert-tail-mode’ is,
but its value is nil. So the problem lies in (buffer-modified-p). It's t
when it should be nil. I evaluated it for Dired buffer in question, it's
t, indeed. Is it correct behavior? What meaning does ‘buffer-modified-p’
have when current buffer is a Dired buffer? Should it ever be t in this
case?
This bug report was last modified 9 years and 310 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.