Re: Inconsistent behavior with comparisons and recursive glob patterns

[Alan Wagner-Krankel <awk@xxxxxxxxxxx>]

Excellent. It's succinct and conveys the necessary information.

Thanks,
Awk

On Tue, May 7, 2024 at 10:08 AM Peter Stephenson
<p.w.stephenson@xxxxxxxxxxxx> wrote:
>
> > On 05/05/2024 07:33 BST Alan Wagner-Krankel <awk@xxxxxxxxxxx> wrote:
> > I think there's some risk that "... '*' may match one or more '/'
> > characters" could be misinterpreted as "... '*' may *only* match one
> > or more '/' characters".
> >
> > Maybe:
> > the patterns `tt(**/)' and `tt(***/)' behave the same as `tt(*/)',
> > i.e. as a standard wildcard tt(*) that could match any set of zero or
> > more characters (including `tt(/)'), followed by a `tt(/)'.
>
> Hmm, I'd perhaps limit that to only the information we wish to add to
> keep it simple...
>
> pws
>
> diff --git a/Doc/Zsh/cond.yo b/Doc/Zsh/cond.yo
> index 000e576..c58aea6 100644
> --- a/Doc/Zsh/cond.yo
> +++ b/Doc/Zsh/cond.yo
> @@ -241,7 +241,11 @@ 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 `tt(*/)', in which the `tt(*)' has its standard behaviour
> +but may also match further `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)',