From: Raymond Nijssen <raymond@es.ele.tue.nl>
To: A.Main@dcs.warwick.ac.uk
Cc: zsh-workers@math.gatech.edu
Subject: Re: quoting bug
Date: Fri, 21 Jun 1996 18:54:18 +0200 (METDST) [thread overview]
Message-ID: <199606211654.SAA06592@krait.es.ele.tue.nl> (raw)
In-Reply-To: <1561.199606211329@stone.dcs.warwick.ac.uk> (message from Zefram on Fri, 21 Jun 1996 14:29:16 +0100 (BST))
::: "Z" == Zefram <A.Main@dcs.warwick.ac.uk> writes:
>> zsh fails to break up strings properly where other shells do the right thing.
> setopt SH_WORD_SPLIT
Thanks for the swift reply. Sorry that it appears to be a FAQ.
I can see the point made in the FAQ regarding the usefulness of this feature.
Mainly for compatibility reasons, I can not see why the incompatible behavior
is the default.
Especially because it's biting me :-{ since setopts are not inherited across
subshell invocations. That is, this doesn't seem to be the case, though I
couldn't find anything in the documentation whether or not that is supposed to
happen.
Also, adding this setopt to my ~/.zshenv doesn't help either since the
subshells start with #!/usr/bin/zsh -f (which is a very useful option to
prevent destruction of the enviroment constructed in the parent script)
So the only two ways around this that I can see are either adding this setopt
to /etc/zshenv, which is clearly unacceptable on a multi-user system, or
modification of all shell scripts .... :-(
Should invoking zsh via a link to `ksh' affect the zsh -f flag? AFAIK, `ksh
-f' is not defined.
-Raymond
prev parent reply other threads:[~1996-06-21 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-21 13:17 Raymond Nijssen
1996-06-21 13:29 ` Zefram
1996-06-21 13:55 ` Bruce Stephens
1996-06-21 14:03 ` Zoltan Hidvegi
1996-06-21 14:24 ` quoting bug, and comparisons with ksh93 Bruce Stephens
1996-06-21 14:37 ` Zoltan Hidvegi
1996-06-21 14:17 ` quoting bug Zefram
1996-06-21 14:30 ` Zoltan Hidvegi
1996-06-21 14:43 ` Hrvoje Niksic
1996-06-21 15:18 ` Zefram
1996-06-21 14:48 ` Chet Ramey
1996-06-21 16:54 ` Raymond Nijssen [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=199606211654.SAA06592@krait.es.ele.tue.nl \
--to=raymond@es.ele.tue.nl \
--cc=A.Main@dcs.warwick.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/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).