From: "Mattias Engdegård" <mattiase@acm.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Muir Manders <muir@mnd.rs>, emacs-devel@gnu.org
Subject: Re: OSX FSEvents file watching support
Date: Thu, 18 Jul 2019 13:52:31 +0200 [thread overview]
Message-ID: <0666D6BD-CEAB-45A2-9A43-27007B03AD1D@acm.org> (raw)
In-Reply-To: <87r26neg8m.fsf@gmx.de>
18 juli 2019 kl. 13.26 skrev Michael Albinus <michael.albinus@gmx.de>:
>
> We have no support for two backends running in parallel. Don't know
> whether this is really wanted.
There is nothing sacred about the current filenotify/backend structure; if it needs changing, then so be it.
Either FSEvents turns out to be able to supplant kqueue on macOS entirely, in which case the point is moot, or we use FSEvent for watching subtrees and keep kqueue for single files and directories.
next prev parent reply other threads:[~2019-07-18 11:52 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0666D6BD-CEAB-45A2-9A43-27007B03AD1D@acm.org \
--to=mattiase@acm.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).