Re: New file notification event `stopped'

[Eli Zaretskii]

> From: Michael Albinus <address@hidden>
> Date: Sat, 10 Oct 2015 12:13:49 +0200
> 
> Nobody did reply.

I did.  Or I thought I did, but now I cannot find my response in the
archives.  Maybe it's my imagination, or maybe it has something to do
with the recent snafu in GNU mailman archives.

Anyway, my response boils down to this: I don't think we should make
notification back-ends invent events that are not reported by the
respective OS facilities.  Doing that is the job of filenotify.el.

In addition, I don't know how to implement this in w32notify.c, at
least not easily.  As I said, when the watched directory is deleted,
the thread that watches exits with an error status, that's all.

What problem should this 'stopped' event solve?  Do we really have a
real-life problem here, and if so, couldn't we solve it in some other
manner?