[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61748: 27.2; Eglot should use shell-file-name when launching the lan
From: |
jeberger |
Subject: |
bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file |
Date: |
Wed, 1 Mar 2023 09:09:53 +0100 (CET) |
"João Távora" <joaotavora@gmail.com> wrote:
> On Tue, Feb 28, 2023 at 4:41 PM <jeberger@free.fr> wrote:
> >
> > Huh, I just noticed that Emacs doesn't use my configured value for
> > `tramp-remote-path`. I've set it through `customize` and it has the
> > correct value in `custom.el` but `C-h v` shows that it has been
> > reset to another value that doesn't include
> > `tramp-own-remote-path`.
>
> Does this mean the bug you experience goes away when
> you add either tramp-own-remote-path or ~/bin to that
> variable and make sure it is set correctly?
>
Adding `tramp-own-remote-path` and making sure that it is set correctly
fixes my point 2, but then `rust-analyzer` doesn't have the path set and
so fails to find the Rust toolchain. So my patch is still required to fix
that part.
Jérôme
- bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file,
jeberger <=
bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file, João Távora, 2023/03/01