zsh-users
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane_chazelas@yahoo.fr>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-users@zsh.org
Subject: Re: {fd}< and compound commands
Date: Thu, 15 Sep 2011 13:58:22 +0100	[thread overview]
Message-ID: <20110915125822.GB5497@yahoo.fr> (raw)
In-Reply-To: <20110914200601.72c91f87@pws-pc.ntlworld.com>

2011-09-14 20:06:01 +0100, Peter Stephenson:
> On Wed, 14 Sep 2011 18:21:48 +0100
> Stephane Chazelas <stephane_chazelas@yahoo.fr> wrote:
> > $ zsh -c '{echo foo >&$fd;}  {fd}> a'
> > zsh:1: parse error near `{'
> > (same for while/do/done constructs at least)
> > 
> > Is that the expected behavior? I can't see it being documented.
> 
> It is documented now.  This is all complicated stuff with wide
> implications for the parser; there's is no chance I will have to time to
> change it myself.
> 
> > That would be useful in
> > 
> > while read <&$fd var; do
> >   ...
> > done {fd}< file
> > 
> > to avoid having to worry about overriding fds 3-9.
> 
> There's no code automatically to close file descriptors anyway.
> Generally, that syntax isn't doing quite what the use of redirection
> syntax would suggest; it's permanently opening a file descriptor, not
> performing a possibly temporary redirection.
[...]

I just noticed ksh93 doesn't close the fd either, though it
supports compound commands:

$ ksh93 -c '{ echo test >&$fd; } {fd}> a; echo foo >&$fd; nl a'
     1  test
     2  foo

I suppose those were primarily meant to be used with "exec".

Looking at the changelogs for ksh93 and zsh, it seems both
shells implemented it within one week of each other (in April
2005), you guys surely must have mentionned it to each other, or
does that feature come from another shell/language?

KSH> 05-04-08 +Redirection operators can be directly preceded with {varname}
KSH>           with no intervening space, where varname is a variable name which
KSH>           allows the shell to select a file descriptor > 10 and store it
KSH>           into varname.

ZSH> 2005-04-12  Peter Stephenson  <pws@csr.com>
[...]
ZSH>         * 21133: Doc/Zsh/redirect.yo, Src/exec.c, Src/parse.c, Src/text.c,
ZSH>         Src/zsh.h, Test/A04redirect.ztst: New {myfd}> syntax for
ZSH>         allocating file descriptors.

-- 
Stephane


  parent reply	other threads:[~2011-09-15 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14 17:21 Stephane Chazelas
2011-09-14 17:36 ` Mikael Magnusson
2011-09-14 19:06 ` Peter Stephenson
2011-09-14 19:31   ` Stephane Chazelas
2011-09-14 21:05     ` Peter Stephenson
2011-09-15 12:58   ` Stephane Chazelas [this message]
2011-09-15 13:09     ` Peter Stephenson
2011-09-15 13:22       ` Chet Ramey
2011-09-15 14:21         ` Stephane Chazelas
2011-09-17 12:21   ` Stephane Chazelas

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=20110915125822.GB5497@yahoo.fr \
    --to=stephane_chazelas@yahoo.fr \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@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).