From: "João Távora" <joaotavora@gmail.com>
To: jeberger@free.fr, 61748-done@debbugs.gnu.org
Cc: Michael Albinus <michael.albinus@gmx.de>
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 [thread overview]
Message-ID: <CALDnm508dpYdsYf8agokzfJXGx3-YxELOrZfgjrKBeTLeZsMnw@mail.gmail.com> (raw)
In-Reply-To: <CALDnm50QHWvX6vqqxgMM1Bq0e-UK_z2aid_SKgjMP6Fr+W6Qpg@mail.gmail.com>
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
next prev parent reply other threads:[~2023-03-07 10:15 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1909672588.15608265.1677223717877.JavaMail.root@zimbra60-e10.priv.proxad.net>
2023-02-24 7:39 ` bug#61748: 27.2; Eglot should use shell-file-name when launching the language server for a remote file jeberger
2023-02-24 8:15 ` Eli Zaretskii
2023-02-24 11:11 ` jeberger
2023-02-24 16:44 ` Michael Albinus
2023-02-27 11:07 ` João Távora
2023-02-27 12:05 ` João Távora
2023-02-27 17:59 ` bug#61748: [informatique] " Jérôme M. Berger
2023-02-27 23:41 ` João Távora
2023-02-28 9:50 ` jeberger
2023-02-28 10:14 ` Michael Albinus
2023-02-28 10:28 ` João Távora
2023-02-27 19:57 ` Michael Albinus
2023-02-27 20:07 ` João Távora
2023-02-27 20:13 ` Michael Albinus
2023-02-28 0:00 ` João Távora
2023-02-28 8:41 ` Michael Albinus
2023-02-28 12:18 ` João Távora
2023-02-28 12:34 ` Michael Albinus
2023-02-28 12:46 ` João Távora
2023-02-28 13:05 ` Michael Albinus
2023-02-28 13:47 ` João Távora
2023-02-28 14:10 ` Michael Albinus
2023-02-28 14:24 ` João Távora
2023-02-28 14:45 ` Michael Albinus
2023-02-28 15:13 ` João Távora
2023-02-28 15:44 ` Michael Albinus
2023-02-28 16:43 ` Eli Zaretskii
2023-02-28 16:49 ` João Távora
2023-02-28 17:56 ` Eli Zaretskii
2023-03-01 4:34 ` Richard Stallman
2023-03-01 9:31 ` João Távora
2023-03-01 13:04 ` Eli Zaretskii
2023-03-01 13:05 ` João Távora
2023-02-28 13:59 ` jeberger
2023-02-28 14:25 ` João Távora
2023-02-28 14:49 ` Michael Albinus
2023-02-28 14:53 ` João Távora
2023-02-28 15:15 ` Michael Albinus
2023-02-28 15:23 ` João Távora
2023-02-28 15:50 ` Michael Albinus
2023-02-28 16:28 ` João Távora
2023-03-02 9:14 ` Michael Albinus
2023-03-02 10:56 ` João Távora
2023-03-02 11:40 ` Michael Albinus
2023-03-03 0:24 ` João Távora
2023-02-28 14:49 ` jeberger
2023-02-28 15:07 ` João Távora
2023-02-28 15:12 ` Michael Albinus
2023-02-28 16:16 ` jeberger
2023-02-28 16:41 ` jeberger
2023-02-28 17:09 ` João Távora
2023-03-01 8:09 ` jeberger
2023-03-02 13:28 ` João Távora
2023-03-07 10:15 ` João Távora [this message]
2023-03-01 8:39 ` Michael Albinus
2023-03-01 8:51 ` jeberger
2023-03-01 9:07 ` Michael Albinus
2023-03-01 10:01 ` jeberger
2023-03-01 10:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALDnm508dpYdsYf8agokzfJXGx3-YxELOrZfgjrKBeTLeZsMnw@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=61748-done@debbugs.gnu.org \
--cc=jeberger@free.fr \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.