From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] quoting within bracket patterns has no effect
Date: Mon, 25 Jan 2016 20:48:29 -0800 [thread overview]
Message-ID: <160125204829.ZM15331@torch.brasslantern.com> (raw)
In-Reply-To: <56A6F01E.8030306@inlv.org>
On Jan 26, 4:03am, Martijn Dekker wrote:
}
} In normal variable expansion, setting the option SH_WORD_SPLIT causes
} unquoted $var to be equivalent to ${~var} in variable expansion.
} Wouldn't it make sense to have SH_WORD_SPLIT activate pattern characters
} in unquoted variables in range expressions as well?
Look again at my first example from the previous message:
schaefer[691] Src/zsh -f
torch% emulate sh
torch% myrange='a-z'
torch% somevar='c'
torch% case $somevar in
case> ( *[$myrange]* ) echo "$somevar is part of $myrange" ;;
case> esac
c is part of a-z
torch% print $ZSH_PATCHLEVEL
zsh-5.2-103-g69c86cd
What about that is incorrect? You need $~myrange for "emulate zsh" but
NOT for "emulate sh", unless I'm missing something.
Also it's never been "setopt shwordsplit" that enables patterns in a
parameter expansion, rather it's "setopt globsubst":
schaefer[692] Src/zsh -f
torch% x='c*h'
torch% print $x
c*h
torch% setopt shwordsplit
torch% print $x
c*h
torch% setopt globsubst
torch% print $x
config.h config.modules.sh
What I was pointing out when I said "I'm not sure it's possible to have
it both ways" has ONLY to do with "emulate zsh". The problem is that
the parsing happens at two different places -- at the time $myrange is
expanded, I don't believe the parameter substitution code knows it's
inside a character set in an active pattern; so there's no way to
temporarily activate globsubst except by explicity doing so.
This may be a case where native zsh is incompatible with POSIX at a
fairly fundamental level; old working zsh scripts are potentially going
to break, and I don't think we can do anything about it unless we want
to tell POSIX to go pound sand.
next prev parent reply other threads:[~2016-01-26 4:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 4:23 Martijn Dekker
2016-01-18 17:24 ` Peter Stephenson
2016-01-19 15:57 ` Jun T.
2016-01-19 17:35 ` Peter Stephenson
2016-01-19 18:54 ` Bart Schaefer
2016-01-20 10:48 ` Jun T.
2016-01-20 11:04 ` Peter Stephenson
2016-01-19 16:03 ` Peter Stephenson
2016-01-19 16:25 ` Mikael Magnusson
2016-01-19 16:34 ` Peter Stephenson
2016-01-19 18:41 ` Bart Schaefer
2016-01-23 0:17 ` Martijn Dekker
2016-01-23 1:49 ` Bart Schaefer
2016-01-26 4:03 ` Martijn Dekker
2016-01-26 4:48 ` Bart Schaefer [this message]
2016-01-26 14:07 ` Martijn Dekker
2016-01-27 3:05 ` Bart Schaefer
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=160125204829.ZM15331@torch.brasslantern.com \
--to=schaefer@brasslantern.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).