GNU bug report logs -
#70792
30.0.50; [PATCH] Add Eshell support for expanding absolute file names within the current remote connection
Previous Next
Full log
Message #92 received at 70792 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 5/9/2024 10:45 PM, Eli Zaretskii wrote:
>> Date: Thu, 9 May 2024 13:30:57 -0700
>> Cc: 70792 <at> debbugs.gnu.org
>> From: Jim Porter <jporterbugs <at> gmail.com>
>>
>> Maybe the better solution would simply be for "/local:"[1] to be an
>> Eshell-only syntax that DTRT within Eshell. There shouldn't be any
>> conflict so long as Tramp promises not to add a "local" method. :)
>
> I agree that it's a better solution: since the problem is Eshell-only,
> having the solution in Eshell has several advantages.
Here's a patch for the first part of this: it just changes the Eshell
syntax for "run this command on localhost even if cwd is remote" to use
"/local:program" instead of "/:program". Now, users can instead use "/:"
in an Eshell command name to *disable* any remote file handlers.
For example "/:/ssh:user <at> remote:/foo" now means, "Run the program 'foo'
on the current host, located in the directory '/ssh:user <at> remote:/'."
Next, I'll work on updating my original patch for this bug to use the
new syntax (possibly with a new way of handling "/local:" if I need it).
I wanted to get this ready first though so that Eshell is in a
release-ready state for the upcoming Emacs 30, even if I don't finish
the rest of this in time.
[0001-Use-local-prefix-in-Eshell-to-run-local-commands-whe.patch (text/plain, attachment)]
This bug report was last modified 1 year and 33 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.