all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: autorevert.el
Date: Mon, 22 Mar 2004 13:39:08 -0600 (CST)	[thread overview]
Message-ID: <200403221939.i2MJd8116508@raven.dms.auburn.edu> (raw)
In-Reply-To: <ud675idbw.fsf@elta.co.il> (message from Eli Zaretskii on 22 Mar 2004 08:51:47 +0200)

Eli Zaretskii wrote:

   I'm at a loss how you arrived at that conclusion, especially since I
   suggested looking at the size for the benefit of systems that cannot
   use the time stamp.  Isn't this better than not knowing the directory
   changed at all?

But the probability of finding it out this way is close to zero.

Stefan Monnier wrote:

   He ment to check it additionally to the mod-time.
   I.e. if either the mod-time or the size has changed, then the dir
   has changed.

Yes, but the size only seems to change after adding or deleting
approximately 200 files.  Many (probably most) of my directories do
not even contain that many files and never will.  They have size 4096
and always will.

What would seem to happen on MS Windows if we did that would be that,
normally, directories do not autorevert, so the user believes that
they never autorevert.  Once in a very blue moon, one huge directory
suddenly starts autoreverting all the time.  The user wonders what is
going on.  All of a sudden it stops autoreverting and never
autoreverts again.  Note that this system is very much biased toward
autoreverting large directories.  Small directories, that would be
very cheap to autorevert, never will be autoreverted.  It would seem
to be relatively better never to autorevert.  Or automatically revert
directories whose size is _below_ a certain threshold every
auto-revert-interval seconds, on systems for which we have no better
method.

Note that to check whether the size has changed, dired needs to store
the old size.  I did not check whether it currently does that.

What if I just go ahead and install my patches to autorevert and
dired?  (Additional changes can always be made later.)  Then maybe
somebody volunteers to solve the portability problem in the only
really correct way.  The problem affects dired proper and ido-mode as
much as it affects auto-revert.  Do the maintainers of the various
ports routinely read emacs-devel?  None appear to be Cc-ed.

Otherwise people using non-POSIX systems can try to set
buffer-stale-function to various values in dired-mode using
dired-mode-hook and see what works best.

Sincerely,

Luc.

  reply	other threads:[~2004-03-22 19:39 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                 ` autorevert.el Luc Teirlinck
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                                 ` Luc Teirlinck [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200403221939.i2MJd8116508@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.