From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: [PATCH 2/2] FAQ (3.1): Update ksh compatibility answer for reserved word typeset.
Date: Thu, 28 May 2020 20:30:49 +0000 [thread overview]
Message-ID: <20200528203049.13144-2-danielsh@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <20200528203049.13144-1-danielsh@tarpaulin.shahaf.local2>
---
Reported in 45922. I dropped the sentence about bash because I couldn't
figure out what it was referring to with the term "this behaviour".
bash on my system does word-split arguments that look like assignments
with backticks on the RHS for commands other than «typeset».
Etc/FAQ.yo | 28 +++++++++++++++++++---------
1 file changed, 19 insertions(+), 9 deletions(-)
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index 9b5e2206a..a327eb514 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -981,7 +981,7 @@ label(31)
been automatic word splitting in scalars, which is a sort of
uncontrollable poor man's array.
- Note that this happens regardless of the value of the internal field
+ Note that word splitting happens regardless of the value of the internal field
separator, tt($IFS); in other words, with mytt(IFS=:; foo=a:b; args $foo)
you get the answer 1.
@@ -1013,22 +1013,32 @@ label(31)
or (entirely equivalent) when mytt(emulate ksh) or mytt(emulate sh) is in
effect.
- There is one other effect of word splitting which differs between ksh
+ There used to be another effect of word splitting which differed between ksh
and zsh. In ksh, the builtin commands that declare parameters such
as tt(typeset) and tt(export) force word-splitting not to take place
after on an assignment argument:
verb(
typeset param=`echo foo bar`
)
- in ksh will create a parameter with value mytt(foo bar), but in zsh will
+ in ksh will create a parameter with value mytt(foo bar).
+
+ zsh used to
create a parameter tt(param) with value tt(foo) and a parameter tt(bar)
- whose value is empty. Contrast this with a normal assignment (no
+ whose value was empty. Contrast this with a normal assignment (no
tt(typeset) or other command in front), which never causes a word split
- unless you have tt(GLOB_ASSIGN) set. From zsh version 4.0.2 the option
- tt(KSH_TYPESET), set automatically in compatibility mode, fixes this
- problem. Note that in bash this behaviour occurs with all arguments that
- look like assignments, whatever the command name; to get this behaviour
- in zsh you have to set the option tt(MAGIC_EQUAL_SUBST).
+ unless you have tt(GLOB_ASSIGN) set.
+
+ zsh version 4.0.2 and newer creates a single parameter with value
+ mytt(foo bar), like ksh does, when the option tt(KSH_TYPESET) is set.
+ This option gets set automatically when in ksh compatibility mode.
+
+ zsh 5.1 and newer create a single parameter with value mytt(foo bar) by
+ default, in both compatibility and native modes. The older behaviour
+ can be obtained with mytt(disable -r typeset).
+
+ If the options mytt(MAGIC_EQUAL_SUBST) and mytt(KSH_TYPESET) are both
+ set, arguments that look like assignments will not undergo word
+ splitting, whatever the command name.
sect(In which startup file do I put...?)
prev parent reply other threads:[~2020-05-28 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 20:30 [PATCH 1/2] FAQ: Add "Why does my bash script report an error when I run it under zsh?" Daniel Shahaf
2020-05-28 20:30 ` Daniel Shahaf [this message]
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=20200528203049.13144-2-danielsh@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).