[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: |
João Távora |
Subject: |
bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file |
Date: |
Tue, 7 Mar 2023 10:15:13 +0000 |
On Thu, Mar 2, 2023 at 1:28 PM João Távora <joaotavora@gmail.com> wrote:
>
> On Wed, Mar 1, 2023 at 8:09 AM <jeberger@free.fr> wrote:
> > `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.
>
> AFAIC is a different problem now. Earlier, the program couldn't be invoked
> at all.
>
> > So my patch is still required to fix that part.
>
> I've pushed a simpler patch to emacs-29. Please test.
I'm going to assume the lack of reply is because the problem
doesn't happen anymore. It doesn't in my tests, but my remote
language server in the remote $HOME doesn't rely on PATH
to figure out the toolchain and thus doesn't suffer from this
vulnerability.
Closing. If the problem persists, we can reopen.
João
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
bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file, Michael Albinus, 2023/03/02