zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Klaus+zsh@Ethgen.ch, zsh-workers@zsh.org
Subject: Re: Undocumented construct <<(
Date: Wed, 18 Nov 2015 14:47:17 +0000	[thread overview]
Message-ID: <20151118144717.0b129f59@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20151118144147.116022ee@pwslap01u.europe.root.pri>

On Wed, 18 Nov 2015 14:41:47 +0000
Peter Stephenson <p.stephenson@samsung.com> wrote:

> On Wed, 18 Nov 2015 15:23:08 +0100
> Klaus Ethgen <Klaus+zsh@Ethgen.ch> wrote:
> > I searched now pretty long for a undocumented construct <<(list).
> 
> What you're looking at is a normal < followed by a <(list),
> i.e. redirect stdin from <(list).

and while I'm sending more emails than necessary, here's a note in the
process substitution documentation.

pws

diff --git a/Doc/Zsh/expn.yo b/Doc/Zsh/expn.yo
index 123722e..564c70d 100644
--- a/Doc/Zsh/expn.yo
+++ b/Doc/Zsh/expn.yo
@@ -410,6 +410,12 @@ are only expanded when first parsing command or assignment arguments.
 Process substitutions may be used following redirection operators; in this
 case, the substitution must appear with no trailing string.
 
+Note that `tt(<<LPAR())var(list)tt(RPAR())' is not a special syntax; it
+is equivalent to `tt(< <LPAR())var(list)tt(RPAR())', redirecting
+standard input from the result of process substitution.  Hence all
+the following documentation applies.  The second form (with the space)
+is recommended for clarity.
+
 In the case of the tt(<) or tt(>) forms, the shell runs the commands in
 var(list) as a subprocess of the job executing the shell command line.
 If the system supports the tt(/dev/fd)


  reply	other threads:[~2015-11-18 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 14:23 Klaus Ethgen
2015-11-18 14:41 ` Peter Stephenson
2015-11-18 14:47   ` Peter Stephenson [this message]
2015-11-18 15:00   ` Klaus Ethgen
2015-11-18 22:55     ` Daniel Shahaf

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=20151118144717.0b129f59@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=Klaus+zsh@Ethgen.ch \
    --cc=zsh-workers@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).