From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Problems with latest CVS.
Date: Mon, 16 Feb 2004 20:49:18 -0600 (CST) [thread overview]
Message-ID: <200402170249.i1H2nIv09314@raven.dms.auburn.edu> (raw)
In-Reply-To: <200402162255.i1GMtis08363@raven.dms.auburn.edu> (message from Luc Teirlinck on Mon, 16 Feb 2004 16:55:44 -0600 (CST))
I believe I figured the problem out. Continuous noisy and
CPU-consuming reverting of dired buffers occurs, _regardless_ of the
value of `global-auto-revert-non-file-buffers', if
global-autorevert-mode is enabled and the user either does not have
the "a" switch in dired-listing-switches or if the user inserts
subdirectories.
There are two problems:
1. `global-auto-revert-non-file-buffers' was ignored for dired
buffers. I already committed a fix to CVS for that one, because
that one seemed to be the urgent one:
`global-auto-revert-non-file-buffers' is a hyper-new option whose
default value is nil.
2. To determine whether a dired buffer has changed,
`auto-revert-dired-changed-p' just counts the number of files in
the dired buffer and compares it with the number of files listed
by (directory-files dired-directory). This is completely
unreliable because of dired-listing-switches, because of inserted
subdirectories, and probably because of other reasons as well.
I did not fix the second problem.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-02-17 2:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 22:37 Problems with latest CVS Luc Teirlinck
2004-02-16 22:47 ` Luc Teirlinck
2004-02-16 22:55 ` Luc Teirlinck
2004-02-17 2:49 ` Luc Teirlinck [this message]
2004-02-17 3:31 ` Luc Teirlinck
2004-02-17 6:43 ` Eli Zaretskii
2004-02-17 16:47 ` Luc Teirlinck
2004-02-17 19:53 ` Luc Teirlinck
2004-02-18 0:08 ` Luc Teirlinck
2004-02-18 0:59 ` Luc Teirlinck
2004-02-18 1:10 ` Luc Teirlinck
2004-02-17 1:37 ` Kim F. Storm
2004-02-17 2:05 ` Luc Teirlinck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200402170249.i1H2nIv09314@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).