From: Bart Schaefer <schaefer@brasslantern.com>
To: Martijn Dekker <martijn@inlv.org>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [doc] "sh_word_split nothing to do with word splitting"?
Date: Fri, 16 Mar 2018 11:28:23 -0700 [thread overview]
Message-ID: <CAH+w=7YHeTQCwfpHGXN=CBHX_4OcGKeMUFytNypaa5CxLDLA5g@mail.gmail.com> (raw)
In-Reply-To: <20180316172613.GB23397@chaz.gmail.com>
On Fri, Mar 16, 2018 at 10:26 AM, Stephane Chazelas
<stephane.chazelas@gmail.com> wrote:
> So, how about this new take at it? Renders (in info) as:
>
> SH_WORD_SPLIT (-y) <K> <S>
> Causes $IFS field splitting to be performed on unquoted parameter
> expansions in addition to command substitutions. Note that
This is OK, I just keep thinking there should be a reference back to
the shell grammar; field splitting applies to anything identified in
the grammar by the token WORD provided that the WORD is not quoted.
Arithmetic expressions are treated as if double-quoted. That's really
all there is to it.
Of course we don't formally spell out the grammer for the basic cases,
instead describing it in prose in the first few paragraphs under
"simple commands" ... and the "general comments on syntax" direct one
to *this* entry, so I suppose the detail is in fact needed here.
next prev parent reply other threads:[~2018-03-16 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 9:44 Stephane Chazelas
2018-03-11 18:24 ` Bart Schaefer
2018-03-11 20:53 ` Stephane Chazelas
2018-03-11 23:41 ` Martijn Dekker
2018-03-12 7:43 ` Stephane Chazelas
2018-03-12 8:07 ` Stephane Chazelas
2018-03-16 17:26 ` Stephane Chazelas
2018-03-16 18:28 ` Bart Schaefer [this message]
2018-03-16 19:33 ` Stephane Chazelas
2018-03-24 20:17 ` Martijn Dekker
2018-03-25 6:42 ` Stephane Chazelas
2018-03-26 18:11 ` Martijn Dekker
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='CAH+w=7YHeTQCwfpHGXN=CBHX_4OcGKeMUFytNypaa5CxLDLA5g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=martijn@inlv.org \
--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).