From: Michael Albinus <michael.albinus@gmx.de>
To: William G. Gardella <wgg2@member.fsf.org>
Cc: 23032@debbugs.gnu.org
Subject: bug#23032: 25.0.91; Eshell misinterprets TRAMP multi-hop paths as pipes
Date: Fri, 18 Mar 2016 10:07:20 +0100 [thread overview]
Message-ID: <87zitwduif.fsf@gmx.de> (raw)
In-Reply-To: <87bn6es89p.fsf@riseup.net> (William G. Gardella's message of "Wed, 16 Mar 2016 16:21:54 +0000")
William G. Gardella <wgg2@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@host|sudo:root@host:
>
> 3. Eshell responds "sudo:root@host:: command not found"
>
> 4. Type the same TRAMP path, but wrapped in quotes:
>
> cd "/sshx:user@host|sudo:root@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@host|sudo:root@host:" and /sshx:user@host\|sudo:root@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.
next prev parent reply other threads:[~2016-03-18 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 16:21 bug#23032: 25.0.91; Eshell misinterprets TRAMP multi-hop paths as pipes William G. Gardella
2016-03-18 9:07 ` Michael Albinus [this message]
2016-03-18 9:11 ` Michael Albinus
[not found] ` <877fgztq2e.fsf@riseup.net>
2016-03-19 15:55 ` Michael Albinus
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=87zitwduif.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=23032@debbugs.gnu.org \
--cc=wgg2@member.fsf.org \
/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).