From: Philip Kaludercic <philipk@posteo.net>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Augusto Stoffel <arstoffel@gmail.com>,
72343@debbugs.gnu.org
Subject: bug#72343: [PATCH] Fix eglot-server-programs for TeX modes
Date: Mon, 12 Aug 2024 16:37:29 +0000 [thread overview]
Message-ID: <8734n98zp2.fsf@posteo.net> (raw)
In-Reply-To: <CALDnm538yLaa_YP8JN6JCcFe2Y-dvfaZYwjSrmpWsugVsDgk7Q@mail.gmail.com> ("João Távora"'s message of "Wed, 7 Aug 2024 14:23:02 +0100")
João Távora <joaotavora@gmail.com> writes:
> On Wed, Aug 7, 2024 at 7:33 AM Augusto Stoffel <arstoffel@gmail.com> wrote:
>
>> By the way, if Eglot relies on that for the multi-language-per-session
>> feature, then such feature would be incompatible with an
>> `eglot-server-program' variable (note the singular) that major modes can
>> set independently as a buffer-local variable.
>
> Yes, I think I mentioned this before. Depends on how you design the feature.
> And you can't just defenestrate eglot-server-programs, you have to keep
> backward compatibility to it.
>
>> Wouldn't it make more sense to reuse a running server if a new one would
>> be started at the same directory and with the same command line
>> arguments?
>
> The feature hasn't been designed so I don't understand the comparative
> "more". But yes, it could make a lot of sense. But instead of "directory",
> "project". And instead of "command line arguments", "contact".
>
> CCing Philip who proposed working on this.
FWIW I have a number of other things on my todo list, and this isn't on
the top for now. So unless I can help and advise someone, this is going
to take a while.
> João
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-08-12 16:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 18:08 bug#72343: [PATCH] Fix eglot-server-programs for TeX modes Augusto Stoffel
2024-07-28 18:20 ` Eli Zaretskii
2024-07-28 21:31 ` João Távora
2024-07-29 6:15 ` Augusto Stoffel
2024-07-29 11:26 ` Eli Zaretskii
2024-07-30 18:20 ` Augusto Stoffel
2024-07-30 20:29 ` João Távora
[not found] ` <CAHixrvYMZTMRSpixw2CAkdx_b+hdPZDkB7s+1X1sUX4E7jPWHw@mail.gmail.com>
[not found] ` <CALDnm50sjTEnSxJ3Rzna3pets2bjHnVF=6vix1gM_54+VoHNvQ@mail.gmail.com>
2024-08-02 15:13 ` Augusto Stoffel
2024-08-02 15:29 ` João Távora
2024-08-06 15:04 ` Augusto Stoffel
2024-08-06 15:34 ` João Távora
2024-08-06 15:45 ` Augusto Stoffel
2024-08-06 16:27 ` João Távora
2024-08-06 16:38 ` Augusto Stoffel
2024-08-06 18:08 ` João Távora
2024-08-06 18:48 ` Augusto Stoffel
2024-08-06 22:52 ` João Távora
2024-08-07 7:02 ` Augusto Stoffel
2024-08-07 8:47 ` João Távora
2024-08-07 9:17 ` Augusto Stoffel
2024-08-07 13:17 ` João Távora
2024-08-07 6:33 ` Augusto Stoffel
2024-08-07 13:23 ` João Távora
2024-08-12 16:37 ` Philip Kaludercic [this message]
2024-08-12 16:53 ` 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=8734n98zp2.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=72343@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@gnu.org \
--cc=joaotavora@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).