From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: How to overcome the (a/b/c…)(N) pattern limitation?
Date: Sat, 18 Apr 2020 16:31:19 +0200 [thread overview]
Message-ID: <CAN=4vMrqRKVwsOLewSiUs_1RuqOXZQLAtHxdsDZ03hw3SoHeiA@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVCDdMUaXYeW0yZU_Cnv=HbNR_w2tRxFcL-Ek3Zi8hvt-w@mail.gmail.com>
On Sat, Apr 18, 2020 at 4:08 PM Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> pick="(/tmp/gh|./gh)"
> list=( ${(M)~pick##/*}(DN) )
I'll simplify:
pick="(/tmp/gh|./gh)"
list=( $~pick )
This doesn't work because $pick contains slashes within parentheses.
This isn't allowed in file generation (with one exception). From the
docs:
(...)
Matches the enclosed pattern. [...]
Note that grouping cannot extend over multiple directories: it is
an error to have a ‘/’ within a group (this only applies for
patterns used in filename generation). There is one exception: a
group of the form (pat/)# appearing as a complete path segment can
match a sequence of directories. For example, foo/(a*/)#bar matches
foo/bar, foo/any/bar, foo/any/anyother/bar, and so on.
Also note that ##/* in your example is applied before file generation.
The effect of the complete example is thus equivalent to this:
pick="(/tmp/gh|./gh)"
tmp=${(M)pick##/*}
list=( ${~tmp}(DN) )
Roman.
next prev parent reply other threads:[~2020-04-18 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 12:49 Sebastian Gniazdowski
2020-04-18 12:55 ` Roman Perepelitsa
2020-04-18 13:41 ` Sebastian Gniazdowski
2020-04-18 13:45 ` Roman Perepelitsa
2020-04-18 14:07 ` Sebastian Gniazdowski
2020-04-18 14:07 ` Sebastian Gniazdowski
2020-04-18 14:31 ` Roman Perepelitsa [this message]
2020-04-18 14:41 ` Sebastian Gniazdowski
2020-04-18 20:00 ` Bart Schaefer
2020-04-18 23:22 ` Sebastian Gniazdowski
2020-04-19 0:02 ` Bart Schaefer
[not found] ` <CAKc7PVCJfCwUUrm5KXzzehxuX1JF=Bvwkh=m7we_TiCrtw_fhQ__30396.4317821496$1587217473$gmane$org@mail.gmail.com>
2020-04-19 6:44 ` Stephane Chazelas
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='CAN=4vMrqRKVwsOLewSiUs_1RuqOXZQLAtHxdsDZ03hw3SoHeiA@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=sgniazdowski@gmail.com \
--cc=zsh-users@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).