Re: New file notification event `stopped'

[Eli Zaretskii]

> From: Michael Albinus <address@hidden>
> Cc: address@hidden
> Date: Sat, 10 Oct 2015 15:35:13 +0200
> 
> Eli Zaretskii <address@hidden> 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.