From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zzapper <zsh@rayninfo.co.uk>,
Mikael Magnusson <mikachu@gmail.com>,
Zsh-Users List <zsh-users@zsh.org>
Subject: Re: Glob Qualifier Yn enables short-circuit mode behaves oddly
Date: Fri, 11 Mar 2022 14:34:15 +0000 (GMT) [thread overview]
Message-ID: <107417053.1338591.1647009255775@mail2.virginmedia.com> (raw)
In-Reply-To: <2218de7b-c1e6-031d-369e-0725d6f605d5@rayninfo.co.uk>
> On 11 March 2022 at 14:12 zzapper <zsh@rayninfo.co.uk> wrote:
> On 11/03/2022 13:50, Mikael Magnusson wrote:
> > On 3/11/22, zzapper <zsh@rayninfo.co.uk> wrote:
> >> Hi
> >>
> >> > print *(.omY3)
> >>
> >> notebash.txt note132.txt note020.txt
> >>
> >> I don't know why it's selected those 3 files but it always does
> >>
> >>
> >> Yn
> >>
> >> enables short-circuit mode: the pattern will expand to at most n
> >> filenames. If more than n matches exist, only the first n matches in
> >> directory traversal order will be considered.
> >>
> >> Implies oN when no oc qualifier is used.
> > You've included the answer in your mail, Y3 will stop looking at files
> > after finding 3 in directory traversal order, those 3 files are then
> > sorted according to their modification timestamp. If you want to
> > consider all files in the directory, use [3] instead of Y3.
>
> So what then is traversal order?
It's totally arbitrary -- whatever the OS throws up. That's the point
of this optimisation --- you've told the shell you don't care what's
there, you're just interested in there being something. I think the
technical answer is likely to be "inode order".
Typical usage of this feature is with a 1 to grab one file that might
be the only one (but if it isn't you don't care).
pws
prev parent reply other threads:[~2022-03-11 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 13:09 zzapper
2022-03-11 13:50 ` Mikael Magnusson
2022-03-11 14:12 ` zzapper
2022-03-11 14:34 ` Peter Stephenson [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=107417053.1338591.1647009255775@mail2.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=mikachu@gmail.com \
--cc=zsh-users@zsh.org \
--cc=zsh@rayninfo.co.uk \
/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).