From: Larry Schrof <larrys@fb.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Bug / error in manpage.
Date: Tue, 2 Oct 2012 17:40:20 +0000 [thread overview]
Message-ID: <CC9074F5.95F1%larrys@fb.com> (raw)
In-Reply-To: <121002070643.ZM28769@torch.brasslantern.com>
Thanks much for taking a look into it and the prompt patch!
On 10/2/12 7:06 AM, "Bart Schaefer" <schaefer@brasslantern.com> wrote:
>On Oct 1, 6:08pm, Larry Schrof wrote:
>}
>} The man page for subscripting flags is incorrect. Here is the excerpt:
>}
>} The flags s, n and b take an argument; the delimiter is shown
>below as
>} `:', but any character, or the matching pairs `(...)',
>`{...}',
>} `[...]', or `<...>', may be used.
>}
>} The '< >' brackets do not work as separators:
>} zsh% print $string[(ws<:>)2]
>} zsh: parse error near `)'
>} zsh%
>
>I see PWS has made a patch, but I just wanted to point out that the man
>page was NOT incorrect before.
>
>It works if you quote it:
>
>torch% print "$string[(ws<:>)2]"
>*
>
>What PWS's patch does, in effect, is arrange that [ ] will quote the
>redirection operators so you no longer need to explicitly quote them in
>that particular context. This is probably breaking some rule or other
>of POSIX shell syntax but I can't immediately come up with any example
>where it will matter.
next prev parent reply other threads:[~2012-10-02 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 18:08 Larry Schrof
2012-10-02 11:57 ` Peter Stephenson
2012-10-02 14:06 ` Bart Schaefer
2012-10-02 17:40 ` Larry Schrof [this message]
2012-10-02 18:35 ` Peter Stephenson
2012-10-02 18:39 ` Larry Schrof
2012-10-02 20:00 ` Peter Stephenson
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=CC9074F5.95F1%larrys@fb.com \
--to=larrys@fb.com \
--cc=schaefer@brasslantern.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).