GNU bug report logs - #61748
27.2; Eglot should use shell-file-name when launching the language server for a remote file

Previous Next

Full log

View this message in rfc822 format

From: João Távora <joaotavora <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: jeberger <at> free.fr, 61748 <at> debbugs.gnu.org
Subject: bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file
Date: Tue, 28 Feb 2023 12:18:22 +0000

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

> João Távora <joaotavora <at> gmail.com> writes:
>
> Hi João,
>
>>     ~/Source/Emacs/emacs/src/emacs -Q                                                 \
>>        /ssh:sshuser <at> localhost#2022:$REMOTE_FILE                                       \
>>        --eval '(add-to-list (quote tramp-remote-path) "~/bin")'                       \
>>        -f eglot
>
> You must set tramp-remote-path before accessing the remote server. Try this:
>
>      ~/Source/Emacs/emacs/src/emacs -Q -l tramp                                        \
>         --eval '(add-to-list (quote tramp-remote-path) "~/bin")'                       \
>         /ssh:sshuser <at> localhost#2022:$REMOTE_FILE                                       \
>         -f eglot

This works, and this would explain the instability I saw earlier.
Thanks.  I wonder if it fixes Jerôme's problem, too.

But IMHO this is a grim pain point for Eglot users expecting things to
"just work".  After all, there I am in the other side thread singing the
praises of Tramp's "transparency", and now it seems that the user be
aware of this Tramp implementation detail -- the early binding of
tramp-remote-path.

Surely we can fix this in Tramp, so that it either considers this
variable's value just-in-time, or detects if there were changes to it
and reacts accordingly.  Can we not?

João

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.