From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Alan Wagner-Krankel <awk@awkwork.com>, zsh-workers@zsh.org
Subject: Re: Inconsistent behavior with comparisons and recursive glob patterns
Date: Wed, 1 May 2024 09:38:48 +0100 (BST) [thread overview]
Message-ID: <1388695268.1045346.1714552728211@mail.virginmedia.com> (raw)
In-Reply-To: <CAGZNKj+TUjbmJLBWV7Rysh0Bs5h=n1e74ukb0rsQye5+5=jBcQ@mail.gmail.com>
> On 01/05/2024 08:55 BST Alan Wagner-Krankel <awk@awkwork.com> wrote:
> Thanks - I did miss that **/ wasn't supported in conditional expressions.
>
> I wonder if there might be some value in making that explicit in the
> documentation, possibly by changing the paragraph you referenced to
> something like this:
>
> Pattern metacharacters are active for the pattern arguments. The patterns
> are the same as those used for filename generation, see zshexpn(1), but
> there is no special behaviour of `/' nor initial dots, shorthand operators
> such as **/ are not converted to their expanded forms, and glob qualifiers
> are only allowed for forcing filenames to be generated as described above.
>
> There's a slight issue that "such as **/" implies there are many
> shorthand operators; I have no idea if there are any others besides
> **/ and ***/.
That's a sensible suggestion, how about this? Please do comment further.
pws
diff --git a/Doc/Zsh/cond.yo b/Doc/Zsh/cond.yo
index 000e576..4216f89 100644
--- a/Doc/Zsh/cond.yo
+++ b/Doc/Zsh/cond.yo
@@ -241,7 +241,10 @@ ifnzman(\
noderef(Filename Generation)\
)\
, but there is no special behaviour
-of `tt(/)' nor initial dots, and no glob qualifiers are allowed.
+of `tt(/)' nor initial dot, and the patterns `tt(**/)' and `tt(***/)' behave
+the same as (*/), in which the tt(*) may match one or more `tt(/)' characters.
+Also, no bare glob qualifiers are allowed, though the form `(#q)var(...)' is
+allowed as shown above.
In each of the above expressions, if
var(file) is of the form `tt(/dev/fd/)var(n)',
next prev parent reply other threads:[~2024-05-01 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGZNKjL2cJhLopFPAFFTewh2cHxX+_L4vMx2Nf9bAS0ud58RBw@mail.gmail.com>
[not found] ` <c97c8fe9-2f56-45b7-bfb2-9f2a97283859@gmx.com>
[not found] ` <CAH+w=7YcdDM6enW37=j3LvOaBnPvazvE9DcHKiJ7VSz-zF7SgQ@mail.gmail.com>
2024-04-30 20:08 ` Bart Schaefer
2024-05-05 6:29 ` Alan Wagner-Krankel
2024-05-01 7:55 ` Alan Wagner-Krankel
2024-05-01 8:38 ` Peter Stephenson [this message]
2024-05-05 6:33 ` Alan Wagner-Krankel
2024-05-07 15:08 ` Peter Stephenson
2024-05-08 5:59 ` Alan Wagner-Krankel
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=1388695268.1045346.1714552728211@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=awk@awkwork.com \
--cc=zsh-workers@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).