From: Michael Albinus <michael.albinus@gmx.de>
To: Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
Cc: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
Brian Cully <bjc@spork.org>
Subject: Re: eglot and tramp
Date: Tue, 15 Nov 2022 16:33:56 +0100 [thread overview]
Message-ID: <875yfgkza3.fsf@gmx.de> (raw)
In-Reply-To: <878rkddngy.fsf@ditto.jhoto.spork.org> (Brian Cully via's message of "Mon, 14 Nov 2022 20:18:37 -0500")
Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
writes:
Hi,
>> I'm looking for some advice on using eglot in a remote TRAMP editing
>> session. I have a couple of scenarios where I'd need to access a VM and
>> edit Python code residing inside. Having a Python LSP that can help me in
>> this use case would be really great.
>>
>> Since there is nothing in the eglot manual about this scenario, I'm asking
>> for enlightenment here
>
> As long as the language server is installed on the remote, it should
> Just Work™.
>
> You may need to add ‘'tramp-own-remote-path’ to ‘tramp-remote-path’,
> depending on where the LSP is installed, however.
It is on my TODO to check how well Tramp is integrated with eglot. Great
to hear that it seems to work flawless, but I believe there might be
some hints for performance improvement, like setting
"direct-async-process" connection property.
When time permits I'll go through this, and I might contribute some few
words to the eglot manual.
> -bjc
Best regards, Michael.
next prev parent reply other threads:[~2022-11-15 15:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 8:20 eglot and tramp Pedro Andres Aranda Gutierrez
2022-11-15 1:18 ` Brian Cully via Emacs development discussions.
2022-11-15 15:33 ` Michael Albinus [this message]
2022-11-15 17:45 ` Brian Cully via Emacs development discussions.
2022-11-15 19:46 ` Michael Albinus
2022-11-16 12:29 ` Brian Cully via Emacs development discussions.
2022-11-16 16:14 ` Michael Albinus
2022-11-18 15:51 ` Michael Albinus
2022-11-19 16:24 ` Brian Cully via Emacs development discussions.
2022-11-20 13:50 ` Michael Albinus
2022-11-21 11:51 ` Brian Cully via Emacs development discussions.
2022-11-21 12:11 ` Michael Albinus
[not found] <87y2oocltq.fsf@gmail.com>
[not found] ` <87pn9v19e8.fsf@gmx.de>
2020-06-19 13:23 ` Eglot and Tramp João Távora
2020-06-19 13:44 ` Michael Albinus
2020-06-19 14:09 ` João Távora
2020-06-19 14:43 ` Michael Albinus
2020-06-19 14:45 ` João Távora
2020-06-19 14:54 ` Michael Albinus
2020-06-19 16:18 ` João Távora
2020-06-19 16:28 ` Michael Albinus
2020-06-19 16:30 ` João Távora
2020-06-19 16:32 ` João Távora
2020-06-19 16:39 ` Michael Albinus
2020-06-19 16:45 ` João Távora
2020-06-19 17:30 ` Michael Albinus
2020-06-19 17:36 ` João Távora
2020-06-19 17:47 ` Dmitry Gutov
2020-06-19 18:01 ` Michael Albinus
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=875yfgkza3.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=bjc@spork.org \
--cc=emacs-devel@gnu.org \
--cc=paaguti@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).