From: Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Brian Cully via Emacs development discussions."
<emacs-devel@gnu.org>,
Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: Re: eglot and tramp
Date: Wed, 16 Nov 2022 07:29:16 -0500 [thread overview]
Message-ID: <8735ajdqw3.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <87v8ng6lxe.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
> Great! Since you are a regular eglot+Tramp user, could I ask you for a
> test?
>
> I assume you are using Tramp with ssh or scp. If you also don't use a
> password (for example via public key authentication), please try the
> following setting:
>
> --8<---------------cut here---------------start------------->8---
> (add-to-list 'tramp-connection-properties
> (list (regexp-quote "/ssh:user@host:")
> "direct-async-process" t))
> --8<---------------cut here---------------end--------------->8---
>
> "/ssh:user@host:" must be adapted of course, and you must set this prior
> opening a connection to this remote path. This should give you better
> performance when starting the language server.
I use eglot+Tramp with various containers (nspawn, docker, podman),
which don't support the ‘tramp-direct-async’ flag, so I'm not sure how
helpful this testing would be.
I know we've spoken about that flag before, and I came away from those
discussions with the impression that those methods should not support
direct-async, but I'm unsure why. I have only skimmed the relevant code,
but it seems like there shouldn't be a problem with supporting
direct-async on the container methods. Is there some danger I should be
aware of?
If it's safe enough, I'd be happy to flag support for direct-async in
the methods and do the above test.
WDYT?
-bjc
next prev parent reply other threads:[~2022-11-16 12:29 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
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. [this message]
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=8735ajdqw3.fsf@ditto.jhoto.spork.org \
--to=emacs-devel@gnu.org \
--cc=bjc@spork.org \
--cc=michael.albinus@gmx.de \
--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).