all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sylvain Chouleur <sylvain.chouleur@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 16582@debbugs.gnu.org
Subject: bug#16582: Bug: tramp shell command doesn't read stdin
Date: Wed, 5 Feb 2014 10:44:03 +0100	[thread overview]
Message-ID: <CAD_mUW3f47FJKSZ8brYRpT1n6-0Tr6n0tFqcFpdCXKeiNx_JUg@mail.gmail.com> (raw)
In-Reply-To: <87zjm6rmi1.fsf@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1975 bytes --]

I'm sorry, may be I was not clear:

replacing EOF by another delimiter does not solve anything, it just make
the way tramp uses heredocs more robust because it avoids conflicts with
user commands potentially using the same delimiter.

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)

-- 
Sylvain


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

> Sylvain Chouleur <sylvain.chouleur@gmail.com> writes:
>
> > Hi Michael,
>
> Hi Sylvain,
>
> > replacing EOF delimiter by a md5sum works well.
>
> Good.
>
> > The process substitution works only for real bash shells, or zsh.
> > It does not work with sh or busybox.
> >
> > So I think we have two solutions here:
> > - Support multiple methods, chosen by user configuration:
> > -> bash -c "cmd" which doesn't support very long commands
> > -> bash <<EOF which doesn't support stdin
> > -> bash <(cat <<EOF) which supports all but which doesn't works on
> > basic shells like sh or busybox (works with bash and zsh)
> > - Reproduce method 3 by writting commands in a target's temporary
> > file, launch the shell with this file in argument, and finally remove
> > the file from the target.
> >
> > The last solution have the major drawback to execute extra commands
> > each time and to have a writable filesystem usable on the target
>
> I don't get your point. If my patch works well (as you said above), why
> do you want to change something else?
>
> If you still have problems with my patch, please give me an exact recipe
> what triggers the problem. I cannot reproduce the problem here, sorry.
> A Tramp debug buffer, produced with tramp-verbose set to 6, would help.
>
> > Cheers,
>
> Best regards, Michael.
>

[-- Attachment #2: Type: text/html, Size: 2860 bytes --]

  reply	other threads:[~2014-02-05  9:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 22:40 bug#16582: Bug: tramp shell command doesn't read stdin Sylvain Chouleur
2014-01-29 14:35 ` 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 [this message]
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_mUW3f47FJKSZ8brYRpT1n6-0Tr6n0tFqcFpdCXKeiNx_JUg@mail.gmail.com \
    --to=sylvain.chouleur@gmail.com \
    --cc=16582@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.