|
From: | Jim Porter |
Subject: | bug#65551: 29.1; Eshell on MS-Windows using plink: 'plink' is not recognized as an internal or external command... |
Date: | Mon, 28 Aug 2023 09:29:50 -0700 |
On 8/28/2023 3:27 AM, Michael Albinus wrote:
I've applied the following sledge-hammer patch, which cures the problem for me. But I'm pretty sure there are better ways in Eshell to fix this.
How about something like this? It's a little less invasive (but no less of a hack).
I'll have to think about this more generally though, since I think Eshell should be a lot more precise about how it handles environment variables on remote hosts in general. Maybe we even want each host to have its own distinct set of env vars. That would probably be safer...
0001-Fix-remote-path-setting-in-Eshell.patch
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |