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 13:28:07 +0300 [thread overview]
Message-ID: <83vbafrpag.fsf@gnu.org> (raw)
In-Reply-To: <87bnc7gheq.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> 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?
next prev parent reply other threads:[~2015-10-10 10:28 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 [this message]
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
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=83vbafrpag.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.