From: Eli Zaretskii <eliz@gnu.org>
To: "Filippo Argiolas" <filippo.argiolas@gmail.com>,
"João Távora" <joaotavora@gmail.com>
Cc: 64608@debbugs.gnu.org
Subject: bug#64608: 29.0.90; Eglot: reuse server when visiting external files
Date: Fri, 14 Jul 2023 13:38:49 +0300 [thread overview]
Message-ID: <837cr24w1y.fsf@gnu.org> (raw)
In-Reply-To: <CAOdrLGJaGGPZw+dHYKRiVdvo2gzJu6j6UKQg+QzO0wBKW3Deyg@mail.gmail.com> (message from Filippo Argiolas on Fri, 14 Jul 2023 07:51:28 +0200)
> From: Filippo Argiolas <filippo.argiolas@gmail.com>
> Date: Fri, 14 Jul 2023 07:51:28 +0200
>
> Hi,
>
> I'm working on a couple of projects each with their main root and all
> sharing some common code in an external root dir.
>
> Each project has a compile_commands.json that knows how to compile the
> external shared code. External root has no compile db and doesn't know
> how to compile itself.
>
> Eglot currently allows me to jump to external files using xref while
> keeping the current active running server by setting
> eglot-extend-to-xref.
>
> Project.el allows me to visit external files using project-or-external-
> functions by defining project-external-roots on my custom backend or
> project-vc-external-roots-functions with the default backend.
>
> It would be great if I configure Eglot to not switch to a new server
> when visiting an external file in a similar way it does with xref.
>
> Any pointer to achieve something like this with current project.el and
> eglot code would also be great. Maybe with a custom project backend?
Sorry, I don't understand: AFAIU Eglot reuses the same server for all
the buffers under the same major-mode, so you should already have what
you want? Or what am I missing?
Adding João to this discussion.
next prev parent reply other threads:[~2023-07-14 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 5:51 bug#64608: 29.0.90; Eglot: reuse server when visiting external files Filippo Argiolas
2023-07-14 10:38 ` Eli Zaretskii [this message]
2023-07-14 13:55 ` Filippo Argiolas
2023-07-14 14:00 ` João Távora
2023-07-15 7:30 ` Filippo Argiolas
2023-07-15 7:32 ` Filippo Argiolas
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=837cr24w1y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64608@debbugs.gnu.org \
--cc=filippo.argiolas@gmail.com \
--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).