Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: strange glob parsing

X-seq: zsh-workers 53728
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Lawrence Velázquez <larryv@xxxxxxx>
Cc: Ryan Rotter <rrotter@xxxxxx>, zsh-workers@xxxxxxx
Subject: Re: strange glob parsing
Date: Mon, 2 Jun 2025 21:32:47 -0700
Archived-at: <https://zsh.org/workers/53728>
In-reply-to: <88fcdb83-cea5-4a35-957c-ffe962497178@app.fastmail.com>
List-id: <zsh-workers.zsh.org>
References: <290D081D-0CE8-487B-ABE8-F217B5CFE707@me.com> <88fcdb83-cea5-4a35-957c-ffe962497178@app.fastmail.com>

On Mon, Jun 2, 2025 at 8:19 PM Lawrence Velázquez <larryv@xxxxxxx> wrote:
>
> It's not what I expect.  I believe that POSIX requires the synonymous
> "[!]" to match a literal '[' followed by a literal '!' followed by
> a literal ']', and bash, dash, and ksh perform matching this way.

There's a comment in pattern.c:

             * []...] means match a "]" or other included characters.
             * However, to be a bit helpful and for compatibility
             * with other shells, don't take in that sense if
             * there's no further "]".  That's still imperfect,
             * but it's all we can do --- we're required to
             * treat [$var]*[$var]with empty var as [ ... ]
             * containing "]*[".

This is followed by a lookahead from ']' to find an optional next ']'.

References:
- strange glob parsing
  - From: Ryan Rotter
- Re: strange glob parsing
  - From: Lawrence Velázquez

Messages sorted by: Reverse Date, Date, Thread, Author