From: Sylvain Chouleur <sylvain.chouleur@gmail.com>
To: 16582@debbugs.gnu.org
Subject: bug#16582: Bug: tramp shell command doesn't read stdin
Date: Tue, 28 Jan 2014 23:40:06 +0100 [thread overview]
Message-ID: <CAD_mUW0ziFEtUcgg6sQE=T0CAW1pfJNfMew+syVn9wHAfz_1mQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hi,
there is a regression introduced by this commit:
e43048325611953396186b569447a3754422ddc3
Author: Michael Albinus <michael.albinus@gmx.de>
Date: Fri Dec 6 16:34:06 2013 +0100
Bug#16045
* progmodes/compile.el (compilation-start):
* progmodes/grep.el (rgrep): Revert change of 2012-12-20 (r111276).
* net/tramp-sh.el (tramp-sh-handle-start-file-process):
Handle long command lines, lasting from "sh -c ...". (Bug#16045)
The following syntax used to execute tramp shell command:
exec <<EOF /bin/bash
commands
EOF
prevents users to send inputs to bash using stdin.
For example, the following does not works anymore:
exec <<EOF /bin/bash
read line;
echo $line;
EOF
I don't understand what was this problem of long command lines (Bug#16045):
I've tried to execute shell comands with huge command lines and all were
successfull.
To keep the approach of splitting the lines, I would suggest something like
that:
exec /bin/bash -c "
commands
on
multiple lines
"
But this needs to backslash all shell specific characters, and I don't know
if there is really benefit compared to the original solution (before <<EOF)
What do you think?
--
Sylvain
PS: I've already posted on tramp-devel mailing list but it seems there is
no activity there.
[-- Attachment #2: Type: text/html, Size: 4618 bytes --]
next reply other threads:[~2014-01-28 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 22:40 Sylvain Chouleur [this message]
2014-01-29 14:35 ` bug#16582: Bug: tramp shell command doesn't read stdin Michael Albinus
2014-02-02 14:27 ` Sylvain Chouleur
2014-02-03 12:53 ` Michael Albinus
2014-02-04 22:53 ` Sylvain Chouleur
2014-02-05 8:29 ` Michael Albinus
2014-02-05 9:44 ` Sylvain Chouleur
2014-02-05 10:27 ` Michael Albinus
2014-02-05 12:27 ` Sylvain Chouleur
2014-02-05 14:04 ` Michael Albinus
2014-02-05 14:44 ` Sylvain Chouleur
2014-02-05 15:33 ` Michael Albinus
2014-02-05 21:01 ` Sylvain Chouleur
2014-02-06 8:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD_mUW0ziFEtUcgg6sQE=T0CAW1pfJNfMew+syVn9wHAfz_1mQ@mail.gmail.com' \
--to=sylvain.chouleur@gmail.com \
--cc=16582@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.