GNU bug report logs - #23032
25.0.91; Eshell misinterprets TRAMP multi-hop paths as pipes

Previous Next

Full log

Message #8 received at 23032 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: William G. Gardella <wgg2 <at> member.fsf.org>
Cc: 23032 <at> debbugs.gnu.org
Subject: Re: bug#23032: 25.0.91;
 Eshell misinterprets TRAMP multi-hop paths as pipes
Date: Fri, 18 Mar 2016 10:07:20 +0100

William G. Gardella <wgg2 <at> member.fsf.org> writes:

Hi William,

> Steps to reproduce:
>
> 1. M-x eshell
>
> 2. Type a TRAMP path that makes an ad-hoc multi-hop connection,
>    such as:
>
>    cd /sshx:user <at> host|sudo:root <at> host:
>
> 3. Eshell responds "sudo:root <at> host:: command not found"
>
> 4. Type the same TRAMP path, but wrapped in quotes:
>
>    cd "/sshx:user <at> host|sudo:root <at> host:"
>
> 5. Eshell successfully navigates to the path.
>
> It seems that eshell too eagerly notices the pipe character
> and assumes that it's reading a piped command line,
> rather than first noticing that the character is inside a TRAMP path.

I don't know whether we can/shall do something about. After all, eshell
is a shell-like command interpreter, and the pipe symbol is a special
one. Like in other shells, special symbols must be escaped. Both
"/sshx:user <at> host|sudo:root <at> host:" and /sshx:user <at> host\|sudo:root <at> host:
work in eshell. Other special symbols, like a space in a filename, would
require similar quoting.

We shall extend the eshell manual pointing about this. Hmm, looks like
the manual even speaks about pipes ...

Best regards, Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.