Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Ilkka Virta <itvirta@iki.fi>
Newsgroups: gnu.bash.bug
Subject: Re: Incorrect example for `[[` command.
Date: Fri, 20 Sep 2019 16:30:17 +0300
Lines: 24
Approved: bug-bash@gnu.org
Message-ID: <mailman.606.1568986234.2190.bug-bash@gnu.org>
References: <CAD0rTC7W20s7-8np7Z+CmZQczTQ+LX=Y1x01gAenewrpiJS5jw@mail.gmail.com> <20190920124827.GP28751@eeg.ccf.org> <70f5667e-d91e-a4cf-fef0-b72c7d61a29a@iki.fi>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
In-Reply-To: <20190920124827.GP28751@eeg.ccf.org>
Content-Language: en-US
Precedence: list
Xref: csiph.com gnu.bash.bug:15382

On 20.9. 15:48, Greg Wooledge wrote:
> but after the regex-glob-thing, it says:
>=20
>    That means values like =E2=80=98aab=E2=80=99 and =E2=80=98 aaaaaab=E2=
=80=99 will match
>=20
> So there's a shift in intent between a? and a+ in what's supposed to be
> a regular expression.  Although of course the sentence is *literally*
> true because the regex would be unanchored, and therefore it's sufficie=
nt
> to match only the 'ab', and the rest of the input doesn't matter.
> But that's just confusing, and doesn't belong in this kind of document.

It goes on to say "as will a line containing a 'b' anywhere in its=20
value", so the text does recognize the zero-width-matching parts don't=20
affect what matches. (I suppose they would affect what goes to=20
BASH_REMATCH[0], but the text doesn't mention that.)

I think it would be a better example with the anchored version also=20
presented for comparison.

--=20
Ilkka Virta / itvirta@iki.fi