From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Jordan Wilson <jordan.t.wilson@gmx.com>, 65551@debbugs.gnu.org
Subject: bug#65551: 29.1; Eshell on MS-Windows using plink: 'plink' is not recognized as an internal or external command...
Date: Sun, 27 Aug 2023 19:55:42 +0200 [thread overview]
Message-ID: <87o7iss735.fsf@gmx.de> (raw)
In-Reply-To: <8e61bce9-e818-c52c-7478-7c11452735ec@gmail.com> (Jim Porter's message of "Sat, 26 Aug 2023 12:16:12 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> 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") "\"")))
This workaround might help in the given situation, but it won't work in
general. The user could apply a multi-hop file name, with plink being
the method of another hop.
Best regards, Michael.
next prev parent reply other threads:[~2023-08-27 17:55 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
2023-08-26 21:28 ` Jordan Wilson
2023-08-27 6:30 ` Jim Porter
2023-08-27 17:55 ` Michael Albinus [this message]
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=87o7iss735.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=65551@debbugs.gnu.org \
--cc=jordan.t.wilson@gmx.com \
--cc=jporterbugs@gmail.com \
/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).