From: "Mattias Engdegård" <mattiase@acm.org>
To: Muir Manders <muir@mnd.rs>
Cc: emacs-devel@gnu.org
Subject: Re: OSX FSEvents file watching support
Date: Thu, 18 Jul 2019 11:54:28 +0200 [thread overview]
Message-ID: <D28B0378-7C5D-419C-87F3-56F970C6E8AF@acm.org> (raw)
In-Reply-To: <0ce358e3-9333-4717-97d5-f03d882bc2d0@www.fastmail.com>
17 juli 2019 kl. 06.18 skrev Muir Manders <muir@mnd.rs>:
>
> I am interested in adding support in Emacs for Mac OS "FSEvents" file watching. FSEvents allows for efficient recursive directory watching, which would be a boon for packages like lsp-mode.
Good!
> 1. Write a new backend for filenotify.el. The existing backends explicitly don't support recursive watching, so I'm not sure if it makes sense to have one special backend that does support recursive watching.
This is probably the way to go, but some careful interface design is necessary. For example, FSEvents only reports the directory where changes occurred. For some applications this may be sufficient, but for others, the exact file names are required. What about lsp-mode? Without a specific application in mind, we risk over-engineering.
FSEvents can probably co-exist with kqueue which fits the filenotify model better for watching individual files, but it would be nice to have something that scales better (kqueue uses up file descriptors). On the other hand, FSEvents may require careful filtering to avoid being swamped with notifications during periods of intensive file system change.
next prev parent reply other threads:[~2019-07-18 9:54 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 [this message]
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
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=D28B0378-7C5D-419C-87F3-56F970C6E8AF@acm.org \
--to=mattiase@acm.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 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).