Subject: Re: bug#8089: Eshell remote files fix (patch)
From: Michael Albinus <[email-masked]>
To: Seppo Sade <[email-masked]>
Cc: [email-masked]
Date: Tue, 22 Feb 2011 06:54:45 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Seppo Sade <[email-masked]> writes:

> The following currently fails in Eshell:
>
> $ sudo bzgrep # Or any shell script in PATH
> /bin/sh: /sudo:root@localhost:/usr/bin/bzgrep: No such file or
> directory
>
> This is apparently so because eshell/sudo translates that to a Tramp
> remote location, but eshell-external-command fails to handle it as a
> remote command. It instead passes the default-directory containing
> Tramp syntax directly to the command (shell script), which obviously
> fails as it doesn't understand Tramp syntax. The patch below fixes
> this issue.

Thanks for the report. I've applied your patch to the trunk (aka Emacs 24).

> (Was there any specific reason for earlier only considering "ftp"
> being remote, instead of all Tramp methods?)

Historical reasons. Originally, eshell used ange-ftp for remote
connections.

Best regards, Michael.