From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: New file notification event `stopped'
Date: Sat, 10 Oct 2015 16:41:28 +0300 [thread overview]
Message-ID: <83d1wmsuwn.fsf@gnu.org> (raw)
In-Reply-To: <8737xihmni.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: emacs-devel@gnu.org
> Date: Sat, 10 Oct 2015 15:35:13 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Imagine you have a file under supervision in auto-revert-mode. If the
> >> watch is broken or removed (by a *-rm-watch call), autorevert could
> >> still work due to the polling mechanism in autorevert.el.
> >
> > Shouldn't it be possible to test the validity from time to time?
>
> autorevert.el, like all other packages using file notifications, could
> install timers for watched files or directories, checking whether there
> are still valid watches. Many timers, and all users of file notification
> need to do the same. It would be a polling behaviour.
No, I meant the single timer we already have there.
> The charm of the `stopped' event would be, that all of this is not
> necessary. Just an event to be handled in the package's file
> notification handler, that's it.
autorevert.el doesn't scale well anyway. E.g., global-autorevert-mode
can potentially consume a lot of system resources (handles etc.) that
are at premium, and we already had a few bug reports for that.
But that's another issue.
next prev parent reply other threads:[~2015-10-10 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 9:08 New file notification event `stopped' Michael Albinus
2015-10-10 10:13 ` Michael Albinus
2015-10-10 10:28 ` Eli Zaretskii
2015-10-10 11:56 ` Michael Albinus
2015-10-10 12:25 ` Eli Zaretskii
2015-10-10 13:35 ` Michael Albinus
2015-10-10 13:41 ` Eli Zaretskii [this message]
2015-10-10 14:35 ` Michael Albinus
2015-10-25 13:21 ` Michael Albinus
2015-10-25 19:57 ` Eli Zaretskii
2015-10-25 22:35 ` Michael Albinus
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=83d1wmsuwn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.