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

Previous Next

Full log

Message #29 received at 16582 <at> debbugs.gnu.org (full text, mbox):

From: Sylvain Chouleur <sylvain.chouleur <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 16582 <at> debbugs.gnu.org
Subject: Re: bug#16582: Bug: tramp shell command doesn't read stdin
Date: Wed, 5 Feb 2014 13:27:17 +0100

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

Go into a tramp buffer, then execute:
(async-shell-command "echo -n \"Type something:\"; read line; echo
line=$line" nil nil)

Your command will print:

Type something:line=

and terminate.
It should have printed

Type something:

waited for your keyboard input and print:

line=<your keyboard input>



2014-02-05 Michael Albinus <michael.albinus <at> gmx.de>:

> Sylvain Chouleur <sylvain.chouleur <at> gmail.com> writes:
>
> > That said, we still have the original issue of the bz I raised:
> > by executing tramp shell commands in this way:
> > exec <<'EOF' bash
> > <commands>
> > EOF
> >
> > we loose the possibility to send user inputs to bash, so commands like
> > 'read' will not work.
> > That's why I proposed the two approaches to handle your problem (long
> > line arguments) and my problem (bash stdin)
>
> Please give me a concrete Lisp example how you invoke this. Otherwise I
> cannot debug; my examples do work.
>
> Alternatively, tell me what you have entered, starting with "M-x".
>
> Best regards, Michael.
>

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

Previous Next

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