From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] quoting within bracket patterns has no effect
Date: Fri, 22 Jan 2016 17:49:49 -0800 [thread overview]
Message-ID: <160122174949.ZM11794@torch.brasslantern.com> (raw)
In-Reply-To: <56A2C6A8.4090108@inlv.org>
On Jan 23, 12:17am, Martijn Dekker wrote:
}
} However, for variables there is now a new problem, the opposite of the
} old one: unlike in every other shell, a range is not recognised even if
} the variable is *not* quoted. So quoting a variable still has no effect,
} it's just that range parsing from variables was disabled altogether. The
} following code:
}
} myrange='a-z'
} somevar='c'
} case $somevar in
} ( *[$myrange]* ) echo "$somevar is part of $myrange" ;;
} esac
}
} outputs "c is part of a-z" on every shell except current zsh.
This is related to long-standing behavior for zsh in native mode.
In as-close-as-zsh-has-to-POSIX mode:
schaefer[655] ARGV0=sh Src/zsh
$ myrange='a-z'
$ somevar='c'
$ case $somevar in
> ( *[$myrange]* ) echo "$somevar is part of $myrange" ;;
> esac
c is part of a-z
$
In native mode you need to use $~param to activate pattern characters
in the expanded value:
schaefer[656] Src/zsh -f
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%
It's true that needing this inside a character class now differs from
previous versions of zsh for native mode. I'm not sure it's possible
to have it both ways.
next prev parent reply other threads:[~2016-01-23 1:49 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 [this message]
2016-01-26 4:03 ` Martijn Dekker
2016-01-26 4:48 ` Bart Schaefer
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=160122174949.ZM11794@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).