unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Elliott Shugerman <eeshugerman@gmail.com>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Landing feature/more-fds for Emacs 30?
Date: Wed, 15 Mar 2023 18:02:01 +0000	[thread overview]
Message-ID: <CALDnm53N=DbxpHk_zcfPTE=vL6mp0znrxEDUvcaSdH6ZMcooGw@mail.gmail.com> (raw)
In-Reply-To: <87wn3hud8z.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

On Wed, Mar 15, 2023, 17:37 Robert Pluim <rpluim@gmail.com> wrote:

> >>>>> On Wed, 15 Mar 2023 17:12:19 +0000, João Távora <
> joaotavora@gmail.com> said:
>
>     João> Hi Elliott,
>     João> On Tue, Mar 14, 2023, 16:10 Elliott Shugerman <
> eeshugerman@gmail.com> wrote:
>
>     >>
>     >> I work on a large codebase with LSP and used to run into the "too
> many
>     >> open files" error all the time unless I disabled desired
> functionality or
>     >> gave up native-comp. Now, with this patch, not only is that issue
> gone
>     >> entirely, but I find Emacs is generally more responsive and stable
> on macOS.
>     >>
>
>     João> What LSP server are you using? Is it perhaps requesting many
> file watchers?
>     João> Or maybe the client is overwatching on the Emacs side (what
> client are you
>     João> using?). Do you have a JSONRPC transcript that you can share
> with me?
>
> Itʼs a macOS thing: file watching there uses a file descriptor
> per-file, unlike Linux, which uses one per-directory.
>

Yes, for sure that should be improved.

But the watches that the client are could also be reduced, perhaps. Maybe,
depending on the use case, it makes sense to only watch files on behalf of
the LSP that Emacs is actually visiting (Eglot doesn't do that, but maybe
it could). All depends on the use case, and that's what I'm interested in.

João

>

[-- Attachment #2: Type: text/html, Size: 2260 bytes --]

  reply	other threads:[~2023-03-15 18:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 16:09 Landing feature/more-fds for Emacs 30? Elliott Shugerman
2023-03-14 17:08 ` Robert Pluim
2023-03-14 19:37   ` Eli Zaretskii
2023-03-15  8:48   ` Michael Albinus
2023-03-15  9:21     ` Robert Pluim
2023-03-15  9:31       ` Michael Albinus
2023-03-15 10:22         ` Robert Pluim
2023-10-03  6:30   ` Stefan Kangas
2023-10-06 10:19     ` Robert Pluim
2023-10-06 11:23       ` Stefan Kangas
2023-10-06 11:52         ` Robert Pluim
2023-10-06 12:13         ` Eli Zaretskii
2023-03-15 17:12 ` João Távora
2023-03-15 17:37   ` Robert Pluim
2023-03-15 18:02     ` João Távora [this message]
     [not found]       ` <CAEb3WWaQM8NskPUqX1S2L_ampAZmv+X+8CwKTxc9urD1rhfexg@mail.gmail.com>
     [not found]         ` <CALDnm51kRCevuZN2=nyjkoxKk4XTxySO1c3e9BWNL-Rvz8B7Vw@mail.gmail.com>
2023-03-25 18:52           ` Elliott Shugerman

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='CALDnm53N=DbxpHk_zcfPTE=vL6mp0znrxEDUvcaSdH6ZMcooGw@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=eeshugerman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    /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).