all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Muir Manders" <muir@mnd.rs>
Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: OSX FSEvents file watching support
Date: Thu, 18 Jul 2019 18:28:49 +0300	[thread overview]
Message-ID: <835znzwedq.fsf@gnu.org> (raw)
In-Reply-To: <d3bf0cd3-a0c6-4312-9a6a-04ef1a183634@www.fastmail.com> (muir@mnd.rs)

> Date: Thu, 18 Jul 2019 08:14:33 -0700
> From: "Muir Manders" <muir@mnd.rs>
> Cc: emacs-devel@gnu.org
> 
> lsp-mode in particular needs to watch your entire source code project for file changes and then relay the file names that were created/modified/deleted fo the LSP server. This is to handle when files change outside the editor, like when changing branches. The LSP server registers file globs for the types of files it wants to receive notifications for, which is normally just the source code files and maybe some project metadata files (e.g. "**/*.go" to watch Go files). The LSP spec delegates file watching to the editor because file watching is hard, and in general there are fewer LSP clients (editors) than LSP servers.
> 
> The current (kqueue, at least) backends must open many file descriptors to watch a large directory tree. FSEvents however can do this task efficiently.

Beware: like I said earlier, I don't expect these facilities to be
scalable enough for watching large trees that get a lot of frequent
changes.  AFAIK, lsp-mode developers recommend to turn off file
notifications when there are a lot of them.



  reply	other threads:[~2019-07-18 15:28 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 [this message]
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=835znzwedq.fsf@gnu.org \
    --to=eliz@gnu.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 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.