Closed jeberger closed 1 year ago
Please report this to the Emacs bug tracker with M-x report-emacs-bug
and put Michael Albinus and me in CC: or X-Debbugs-CC:
. I have very little TRAMP experience.
Please report this to the Emacs bug tracker with
M-x report-emacs-bug
and put Michael Albinus and me in CC: orX-Debbugs-CC:
. I have very little TRAMP experience.
Done: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61748 but I couldn't put you or Michael Albinus in CC since I don't have your email addresses.
Closing. Let's continue in that bug. I've also reproduced the problem in the meantime, and it's indeed a bit annoying.
Steps to reproduce:
rust-analyzer
, which installs in a subdirectory under$HOME
and not/usr/bin
)sh
(e.g. set the path in.zprofile
forzsh
).shell-file-name
to the shell you're using on the remote (e.g.(setq shell-file-name "zsh")
)Expected result:
Eglot should start
Actual result:
Eglot asks
Enter program to execute (or <host>:<port>):
, then when I typerust-analyzer
it fails with message[jsonrpc] Server exited with status 127
. Looking ateglot-events-buffer
, it is clear that eglot tried to usesh
to start the server.Partial fix
The server starts correctly if I change function
eglot--cmd
to use(or shell-file-name "sh")
instead of plain"sh"
, e.g.:It still fails to autodetect the server and asks for the program to execute though.