From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [doc] "sh_word_split nothing to do with word splitting"?
Date: Sun, 11 Mar 2018 09:44:58 +0000 [thread overview]
Message-ID: <20180311094458.GA6450@chaz.gmail.com> (raw)
SH_WORD_SPLIT (-y) <K> <S>
Causes field splitting to be performed on unquoted parameter
expansions. Note that this option has nothing to do with word
splitting. (See *note Parameter Expansion::.)
[...]
${=SPEC}
Perform word splitting using the rules for SH_WORD_SPLIT during the
evaluation of SPEC, but regardless of whether the parameter appears
in double quotes; if the '=' is doubled, turn it off. This forces
parameter expansions to be split into separate words before
substitution, using IFS as a delimiter. This is done by default in
most other shells.
Note that splitting is applied to WORD in the assignment forms of
SPEC _before_ the assignment to NAME is performed. This affects
the result of array assignments with the A flag.
It's unclear to me what is meant by "Note that this option has
nothing to do with word splitting" here.
It seems the SH_WORD_SPLIT description makes a distinction
between "field splitting" and "word splitting", but then again
throughout the manual (including the $=spec description above),
"word splitting" and "field splitting" are used interchangeably
to refer to the same thing.
Was the intended meaning something like: "Note that it does not
affect how the shell delimits tokens" or something like that?
From:
https://unix.stackexchange.com/questions/26661/what-is-word-splitting-why-is-it-important-in-shell-programming
--
Stephane
next reply other threads:[~2018-03-11 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 9:44 Stephane Chazelas [this message]
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
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=20180311094458.GA6450@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--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).