From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: autorevert.el
Date: Mon, 15 Mar 2004 22:56:31 -0600 (CST) [thread overview]
Message-ID: <200403160456.i2G4uVL14097@raven.dms.auburn.edu> (raw)
In-Reply-To: <u3c8ar3q4.fsf@elta.co.il> (message from Eli Zaretskii on 15 Mar 2004 09:04:03 +0200)
Eli Zaretskii wrote:
> For dired buffers, visited-file-modtime works
Only on Posix systems, btw. On MS-Windows, the directory's time
stamp does not change when you add or remove files.
That would mean that on MS-Windows, you also would not always (or even
rarely) get the "Directory has changed on disk; type g to update Dired"
massages by which dired warns you that the information you are getting
is obsolete. Indeed, the way Auto Revert Mode would check whether a
dired buffer needs reverting _after my patch is applied_ would be
identical to the way Dired decides whether it needs to print that message.
Anyway, I believe I have no choice but to change the current handling
of dired buffers by autorevert, because the present code is wrong and
chews up tons of CPU. I have the impression that the current code
takes substantially more time checking whether a dired buffer needs
reverting than it would take to actually revert it. On top of that,
the results of the check are completely incorrect.
What this could mean is that autoreverting of dired buffers may not
work on MS-Windows or maybe that, on MS-windows, one could just
automatically autorevert dired buffers every auto-revert-interval
seconds, assuming one has a reasonably fast computer (admittedly a
very suboptimal solution).
Once I have actually applied my patch, people could experiment and see
what really happens on various operating systems.
Sincerely,
Luc.
next prev parent reply other threads:[~2004-03-16 4:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 23:19 autorevert.el Luc Teirlinck
2004-03-03 13:24 ` autorevert.el Stefan Monnier
2004-03-04 5:08 ` autorevert.el Luc Teirlinck
2004-03-04 20:43 ` autorevert.el Stefan Monnier
2004-03-05 4:00 ` autorevert.el Luc Teirlinck
2004-03-13 3:10 ` autorevert.el Luc Teirlinck
2004-03-13 11:29 ` autorevert.el Kai Grossjohann
2004-03-14 23:15 ` autorevert.el Stefan Monnier
2004-03-15 0:08 ` autorevert.el Luc Teirlinck
2004-03-15 2:58 ` autorevert.el Stefan Monnier
2004-03-15 7:04 ` autorevert.el Eli Zaretskii
2004-03-16 4:56 ` Luc Teirlinck [this message]
2004-03-16 19:40 ` autorevert.el Eli Zaretskii
2004-03-19 4:48 ` autorevert.el Luc Teirlinck
2004-03-19 6:06 ` autorevert.el Stefan Monnier
2004-03-21 2:42 ` autorevert.el Luc Teirlinck
2004-03-23 15:26 ` autorevert.el Stefan Monnier
2004-03-24 4:20 ` autorevert.el Luc Teirlinck
2004-03-24 4:25 ` autorevert.el Luc Teirlinck
2004-03-21 4:19 ` autorevert.el Luc Teirlinck
2004-03-19 10:19 ` autorevert.el Kim F. Storm
2004-03-19 14:46 ` autorevert.el Eli Zaretskii
2004-03-21 3:26 ` autorevert.el Luc Teirlinck
2004-03-21 6:46 ` autorevert.el Eli Zaretskii
2004-03-22 2:44 ` autorevert.el Luc Teirlinck
2004-03-22 6:51 ` autorevert.el Eli Zaretskii
2004-03-22 19:39 ` autorevert.el Luc Teirlinck
2004-03-23 19:40 ` autorevert.el Eli Zaretskii
2004-03-23 20:09 ` autorevert.el Stefan Monnier
2004-03-24 4:10 ` autorevert.el Luc Teirlinck
2004-03-24 6:58 ` autorevert.el Eli Zaretskii
2004-03-24 18:03 ` autorevert.el Stefan Monnier
2004-03-25 6:56 ` autorevert.el Eli Zaretskii
2004-03-25 17:01 ` autorevert.el Stefan Monnier
2004-03-24 18:56 ` autorevert.el Luc Teirlinck
2004-03-25 6:20 ` autorevert.el Luc Teirlinck
2004-03-25 6:49 ` autorevert.el Luc Teirlinck
2004-03-25 7:21 ` autorevert.el Eli Zaretskii
2004-03-22 19:47 ` autorevert.el Luc Teirlinck
2004-03-22 16:23 ` autorevert.el Stefan Monnier
2004-03-23 4:24 ` autorevert.el Eli Zaretskii
2004-03-21 19:22 ` autorevert.el Richard Stallman
2004-03-16 5:06 ` autorevert.el Luc Teirlinck
2004-03-05 4:25 ` autorevert.el Luc Teirlinck
2004-03-05 5:55 ` autorevert.el Luc Teirlinck
2004-03-04 5:34 ` autorevert.el 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=200403160456.i2G4uVL14097@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).