From: "João Távora" <joaotavora@gmail.com>
To: Niels Thykier <niels@thykier.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 72088@debbugs.gnu.org
Subject: bug#72088: eglot: Segregates language servers in a way that hampers polyglot language servers
Date: Sun, 14 Jul 2024 10:48:32 +0100 [thread overview]
Message-ID: <CALDnm51jEzLYmyDMdT2o=O2JXhFZ52NfDNsVKypaKhMsnNoVuA@mail.gmail.com> (raw)
In-Reply-To: <e414cbdd-b9bc-43c6-aa10-42f15118faac@thykier.net>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Sun, Jul 14, 2024, 10:36 Niels Thykier <niels@thykier.net> wrote:
> I read through
>
> https://www.gnu.org/software/emacs/manual/html_node/eglot/Setting-Up-LSP-Servers.html
> and I do not see anything here that decides how to control whether one
> or two instances per project will be spawned.
>
In that section, did you happen to read this sentence?
"In addition, major-mode can be a list of several major modes specified in
one of the above forms – this means a running instance of the associated
server is responsible for files of multiple major modes or languages in the
project. "
If so, how do you comprehend or interpret it? Maybe it could be clarified.
Regardless, the default value of the eglot-server-programs variable that
ships with Emacs has several examples that make use of this feature, so it
may be worth studying those.
João
[-- Attachment #2: Type: text/html, Size: 1532 bytes --]
next prev parent reply other threads:[~2024-07-14 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 11:33 bug#72088: eglot: Segregates language servers in a way that hampers polyglot language servers Niels Thykier
2024-07-13 6:15 ` Eli Zaretskii
2024-07-13 16:29 ` João Távora
2024-07-14 4:37 ` Eli Zaretskii
2024-07-14 7:31 ` Niels Thykier
2024-07-14 8:01 ` João Távora
2024-07-14 9:36 ` Niels Thykier
2024-07-14 9:46 ` Niels Thykier
2024-07-14 10:30 ` Niels Thykier
2024-07-14 9:48 ` João Távora [this message]
2024-07-14 12:01 ` Niels Thykier
2024-07-14 13:21 ` João Távora
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='CALDnm51jEzLYmyDMdT2o=O2JXhFZ52NfDNsVKypaKhMsnNoVuA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=72088@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=niels@thykier.net \
/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).