unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>,
	"Brian Cully via Emacs development discussions."
	<emacs-devel@gnu.org>
Cc: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: Re: eglot and tramp
Date: Tue, 15 Nov 2022 12:45:24 -0500	[thread overview]
Message-ID: <875yfgdscr.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <875yfgkza3.fsf@gmx.de>

Michael Albinus <michael.albinus@gmx.de> writes:

> 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.

I wouldn't go so far as to say "flawlessly". It does often run into the
"forbidden re-entrant call to Tramp" problem, but that's not unique to
Eglot, and it doesn't seem to cause any problems other than an annoying
message periodically in the echo area.

Otherwise it works pretty well. I've been using it like this for years,
and am pretty happy with it.

-bjc



  reply	other threads:[~2022-11-15 17:45 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. [this message]
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=875yfgdscr.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).