From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Muir Manders <muir@mnd.rs>, emacs-devel@gnu.org
Subject: Re: OSX FSEvents file watching support
Date: Thu, 18 Jul 2019 13:31:10 +0200 [thread overview]
Message-ID: <87muhbeg01.fsf@gmx.de> (raw)
In-Reply-To: <83lfwvy9ai.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Jul 2019 12:35:49 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> 3. Publish an elisp package that calls out to an existing program
>> that supports FSEvents like "fswatch". This
>> approach probably has the least friction, but doesn't allow for
>> tweaking FSEvents settings, and might have
>> performance disadvantages.
>
> How would that work, implementation-wise? Filesystem events are
> supposed to be eventually injected into the input queue; how would you
> go about doing that when an external porgram does the watching?
Tramp mimics this by calling the respective special event filter function
file-notify-handle-event. See tramp-sh-inotifywait-process-filter and
tramp-sh-gio-monitor-process-filter.
Best regards, Michael.
next prev parent reply other threads:[~2019-07-18 11:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 4:18 OSX FSEvents file watching support Muir Manders
2019-07-17 19:26 ` Michael Albinus
2019-07-18 9:35 ` Eli Zaretskii
2019-07-18 11:31 ` Michael Albinus [this message]
2019-07-18 12:00 ` Eli Zaretskii
2019-07-18 12:16 ` Michael Albinus
2019-07-18 12:30 ` Eli Zaretskii
2019-07-18 14:14 ` Michael Albinus
2019-07-18 14:18 ` Eli Zaretskii
2019-07-18 14:29 ` Michael Albinus
2019-07-18 14:55 ` Stefan Monnier
2019-07-18 15:03 ` Michael Albinus
2019-07-18 14:30 ` Eli Zaretskii
2019-07-18 14:46 ` Michael Albinus
2019-07-18 15:14 ` Muir Manders
2019-07-18 15:28 ` Eli Zaretskii
2019-07-18 18:04 ` Michael Albinus
2019-07-18 14:38 ` Muir Manders
2019-07-18 9:54 ` Mattias Engdegård
2019-07-18 11:26 ` Michael Albinus
2019-07-18 11:52 ` Mattias Engdegård
2019-07-18 14:53 ` Muir Manders
2019-07-18 15:06 ` Stefan Monnier
2019-07-18 16:47 ` Mattias Engdegård
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=87muhbeg01.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=muir@mnd.rs \
/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.