|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#16582: closed (Bug: tramp shell command doesn't read stdin) |
Date: | Thu, 06 Feb 2014 08:53:02 +0000 |
Your message dated Thu, 06 Feb 2014 09:52:24 +0100 with message-id <address@hidden> 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 address@hidden) -- 16582: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16582 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: Bug: tramp shell command doesn't read stdin Date: Tue, 28 Jan 2014 23:40:06 +0100 Hi,there is a regression introduced by this commit:e43048325611953396186b569447a3754422ddc3Author: Michael Albinus <address@hidden>Date: Fri Dec 6 16:34:06 2013 +0100Bug#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/bashcommandsEOFprevents users to send inputs to bash using stdin.For example, the following does not works anymore:exec <<EOF /bin/bashread line;echo $line;EOFI 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 "commandsonmultiple 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?--SylvainPS: I've already posted on tramp-devel mailing list but it seems there is no activity there.
--- End Message ---
--- Begin Message ---Subject: Re: bug#16582: Bug: tramp shell command doesn't read stdin Date: Thu, 06 Feb 2014 09:52:24 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Sylvain Chouleur <address@hidden> 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.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |