From: Jim <linux.tech.guy@gmail.com>
To: zsh <zsh-users@zsh.org>
Subject: Re: glob inside nested parameter expansion returns glob string
Date: Thu, 21 Apr 2022 16:00:15 -0500 [thread overview]
Message-ID: <CA+rB6G+bMAXc9gcXXNmPu1=UUnq_xwgEsZ3cHZvd7ZMSdVnFsQ@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6GLFxhafn1OcRKHsxE-05b8VNpPt19PzZBCbOuu2=uv-Qg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Sorry, thought I had extendedglob set, works fine.
On Thu, Apr 21, 2022 at 3:37 PM Jim <linux.tech.guy@gmail.com> wrote:
> Thanks everyone for the responses.
>
> On Thu, Apr 21, 2022 at 2:15 PM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
>> On Thu, Apr 21, 2022 at 11:51 AM Mikael Magnusson <mikachu@gmail.com>
>> wrote:
>> >
>> > On 4/21/22, Jim <linux.tech.guy@gmail.com> wrote:
>> > >
>> > > % A=(${:-.z*(.N)})
>> > > % A=(${A:#*(comp|hist)*})
>> > >
>> > > Is there a way to nest the two?
>> >
>> > There is a certain order that parameter expansions and globs happen
>> > relative to eachother [...] In short, no(t as far as I know).
>>
>> Correct, this can't be done as a nested expansion, except by invoking
>> a subshell to perform the globbing.
>>
>> A=(${${(@f):-$(print -rl .z*(.N))}:#*(comp|hist)*})
>>
>
> Came fairly close on this one while trying different ways. Didn't use a
> print
> command. :-(
>
> However, with extendedglob this specific example can be done entirely
>> with globbing:
>>
>> A=( .z*~*(comp|hist)*(.N) )
>>
>
> Is there a typo or something missing here? This didn't find any files when
> I
> cut and pasted it in a shell.
>
> ZSH_VERSION 5.8
> ZSH_PATCHLEVEL debian/5.8-6+deb11u1
>
> Again, thanks,
>
> Jim Murphy
>
[-- Attachment #2: Type: text/html, Size: 2362 bytes --]
prev parent reply other threads:[~2022-04-21 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 17:24 Jim
2022-04-21 18:51 ` Mikael Magnusson
2022-04-21 19:15 ` Bart Schaefer
2022-04-21 20:37 ` Jim
2022-04-21 21:00 ` Jim [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='CA+rB6G+bMAXc9gcXXNmPu1=UUnq_xwgEsZ3cHZvd7ZMSdVnFsQ@mail.gmail.com' \
--to=linux.tech.guy@gmail.com \
--cc=linuxtechguy@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).