GNU bug report logs - #16582
Bug: tramp shell command doesn't read stdin

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#16582: closed (Bug: tramp shell command doesn't read stdin)
Date: Thu, 06 Feb 2014 08:53:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 06 Feb 2014 09:52:24 +0100
with message-id <87iossei7r.fsf <at> gmx.de>
and subject line Re: bug#16582: Bug: tramp shell command doesn't read stdin
has caused the debbugs.gnu.org bug report #16582,
regarding Bug: tramp shell command doesn't read stdin
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
16582: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16582
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Sylvain Chouleur <sylvain.chouleur <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Bug: tramp shell command doesn't read stdin
Date: Tue, 28 Jan 2014 23:40:06 +0100

[Message part 3 (text/plain, inline)]

 Hi,

there is a regression introduced by this commit:

e43048325611953396186b569447a3754422ddc3
Author: Michael Albinus <michael.albinus <at> 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.

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Sylvain Chouleur <sylvain.chouleur <at> gmail.com>
Cc: 16582-done <at> debbugs.gnu.org
Subject: Re: bug#16582: Bug: tramp shell command doesn't read stdin
Date: Thu, 06 Feb 2014 09:52:24 +0100

Sylvain Chouleur <sylvain.chouleur <at> gmail.com> writes:

> that's great! I didn't think about this one, it works very well.

I've committed the patch, closing the bug.

Best regards, Michael.

Previous Next

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