From: Stephane Chazelas <stephane@chazelas.org>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>,
Zsh Users <zsh-users@zsh.org>
Subject: Re: How to overcome the (a/b/c…)(N) pattern limitation?
Date: Sun, 19 Apr 2020 07:44:56 +0100 [thread overview]
Message-ID: <20200419064456.uojmjqicszxfivvl@chazelas.org> (raw)
In-Reply-To: <CAKc7PVCJfCwUUrm5KXzzehxuX1JF=Bvwkh=m7we_TiCrtw_fhQ__30396.4317821496$1587217473$gmane$org@mail.gmail.com>
2020-04-18 15:41:37 +0200, Sebastian Gniazdowski:
> On Sat, 18 Apr 2020 at 14:56, Roman Perepelitsa <roman.perepelitsa@gmail.com>
> wrote:
>
> > On Sat, Apr 18, 2020 at 2:51 PM Sebastian Gniazdowski
> > <sgniazdowski@gmail.com> wrote:
> > > I was trying to do: ls (/tmp/somedir/gh|./gh)(N)
> >
> > This should work:
> >
> > ls {/tmp/somedir/gh,./gh}(N)
> >
> > Note that you'll get listing for the current directory if there are no
> > matches.
> >
> > Roman.
> >
>
> I need the technique to be pattern-based – it is used in script in a
> $~pattern way.
[...]
Use an array:
pattern=({/tmp/somedir/gh,./gh}'(N)')
ls -ld -- $~pattern
--
Stephane
prev parent reply other threads:[~2020-04-19 6:45 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
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 [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=20200419064456.uojmjqicszxfivvl@chazelas.org \
--to=stephane@chazelas.org \
--cc=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).