unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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:11:43 +0100	[thread overview]
Message-ID: <87vb4kdub4.fsf@gmx.de> (raw)
In-Reply-To: <87zitwduif.fsf@gmx.de> (Michael Albinus's message of "Fri, 18 Mar 2016 10:07:20 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

> 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 ...

PS: The eshell manual documents this already in general, see
(info "(eshell) Arguments")

But it still doesn't explain that it supports piped command
sequences. This shall be added.

Best regards, Michael.





  reply	other threads:[~2016-03-18  9:11 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
2016-03-18  9:11   ` Michael Albinus [this message]
     [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=87vb4kdub4.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).