From: Jim Porter <jporterbugs@gmail.com>
To: Jordan Wilson <jordan.t.wilson@gmx.com>,
65551@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#65551: 29.1; Eshell on MS-Windows using plink: 'plink' is not recognized as an internal or external command...
Date: Sat, 26 Aug 2023 12:16:12 -0700 [thread overview]
Message-ID: <8e61bce9-e818-c52c-7478-7c11452735ec@gmail.com> (raw)
In-Reply-To: <861qfpnb9y.fsf@gmx.com>
On 8/26/2023 7:11 AM, Jordan Wilson wrote:
> I've found a bug in Eshell on MS-Windows on 29.1. This is a regression
> from 28.2. When connected to a remote machine using putty's "plink",
> using any commands on the remote machine (e.g. not built-in to eshell)
> prints this error in the eshell buffer (details replaced):
Thanks for reporting this. I can reproduce this issue. Does evaluating
the following work?
(setf (alist-get 'tramp-login-program
(alist-get "plink" tramp-methods nil nil #'equal))
(list (concat "\"" (executable-find "plink") "\"")))
If so, I think I've identified the bug: in
'eshell-gather-process-output', we set the 'process-environment' to
Eshell's environment variables. In a remote directory, this includes the
remote PATH. However, that confuses Tramp, which uses that remote PATH
to look for the local "plink.exe".
Michael, what would be the best way to handle this? In Eshell, I want to
be able to call 'make-process' to start a remote process using the local
system's default 'process-environment', but for the remote process to
see Eshell's modified environment variables. I see that there's
'tramp-remote-process-environment', but I'm not sure that's the right
thing for me to use. Do you have any ideas?
next prev parent reply other threads:[~2023-08-26 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 14:11 bug#65551: 29.1; Eshell on MS-Windows using plink: 'plink' is not recognized as an internal or external command Jordan Wilson
2023-08-26 14:42 ` Eli Zaretskii
2023-08-26 14:48 ` Jordan Wilson
2023-08-26 15:12 ` Eli Zaretskii
2023-08-26 19:16 ` Jim Porter [this message]
2023-08-26 21:28 ` Jordan Wilson
2023-08-27 6:30 ` Jim Porter
2023-08-27 17:55 ` Michael Albinus
2023-08-27 17:50 ` Michael Albinus
2023-08-27 18:48 ` Jim Porter
2023-08-28 10:27 ` Michael Albinus
2023-08-28 16:29 ` Jim Porter
2023-08-28 16:47 ` Jim Porter
2023-08-28 16:53 ` Jim Porter
2023-08-28 17:40 ` Michael Albinus
2023-09-08 1:18 ` Jim Porter
2023-08-28 17:33 ` Michael Albinus
2023-08-28 18:01 ` Jim Porter
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e61bce9-e818-c52c-7478-7c11452735ec@gmail.com \
--to=jporterbugs@gmail.com \
--cc=65551@debbugs.gnu.org \
--cc=jordan.t.wilson@gmx.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).