unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Brian Cully <bjc@spork.org>
Cc: "Brian Cully via Emacs development discussions."
	<emacs-devel@gnu.org>,
	Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: Re: eglot and tramp
Date: Sun, 20 Nov 2022 14:50:54 +0100	[thread overview]
Message-ID: <877czpg2f5.fsf@gmx.de> (raw)
In-Reply-To: <87mt8mzzcm.fsf@ditto.jhoto.spork.org> (Brian Cully's message of "Sat, 19 Nov 2022 11:24:41 -0500")

Brian Cully <bjc@spork.org> writes:

Hi Brian,

>> Locally, I have tested it with the methods "docker" and "kubernetes", it
>> seems to work. I couldn't test with "podman", because I haven't such a
>> system just now.
>
> I've applied your patch, and will get back to you after I've used it for
> a few days. So far, so good, though. Is there any behavior I should be
> paying special attention to?

Hmm, does it show better performance when accessing an lsp server?

Otherwise, special restrictions for Tramp's direct async processes are
domented at (info "(tramp)Improving performance of asynchronous remote processes").

>> For "nspawn" I cannot say anything, I don't use it. Perhaps it is
>> sufficient to add a similar line in its tramp-methods specification,
>> don't know. You as author might know it better. And if it works
>> sufficiently, we might also think about integrating it into
>> tramp-container.el. But this would be another story.
>
> If nspawn-style containers are desirable in mainline Tramp, I can put
> together a patch for you when I get some cycles.

Yes, it would be welcome in tramp-container.el. Even if it doesn't
support direct-async (yet).

> -bjc

Best regards, Michael.



  reply	other threads:[~2022-11-20 13:50 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.
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 [this message]
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=877czpg2f5.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).