From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@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:41:13 +0200 [thread overview]
Message-ID: <CAKc7PVBegZaHrarNexZ7Gc-=G50JqaezMEY80Ay=Ru8y9E_yjA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMrqRKVwsOLewSiUs_1RuqOXZQLAtHxdsDZ03hw3SoHeiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
On Sat, 18 Apr 2020 at 16:31, Roman Perepelitsa <roman.perepelitsa@gmail.com>
wrote:
> 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. [...]
> …
>
Yes, but as I wrote, such patterns are useful, good ones and I'm looking
for an alternative form for them.
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) )
>
Yes, I simplified the case again, the complete example is:
list=( ${(M)~ZINIT_ICE[pick]##/*}(DN)
$local_dir/$dirname/${~ZINIT_ICE[pick]##/*}(DN.) )
It matches either the absolute path given in pick, or applies it inside the
local directory.
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zinit
Blog: http://zdharma.org
next prev parent reply other threads:[~2020-04-18 14:43 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
2020-04-18 14:41 ` Sebastian Gniazdowski [this message]
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='CAKc7PVBegZaHrarNexZ7Gc-=G50JqaezMEY80Ay=Ru8y9E_yjA@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=roman.perepelitsa@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).