Re: Incorrect example for `[[` command.

Path	csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From	hk <hkadeveloper@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Incorrect example for `[[` command.
Date	Sat, 21 Sep 2019 20:47:52 +0800
Lines	27
Approved	bug-bash@gnu.org
Message-ID	<mailman.727.1569070092.2190.bug-bash@gnu.org> (permalink)
References	<CAD0rTC7W20s7-8np7Z+CmZQczTQ+LX=Y1x01gAenewrpiJS5jw@mail.gmail.com> <8e7c8ea4-2fdf-4809-0b50-ea1bfbbec165@case.edu> <CAD0rTC68qoXvCV9SLP1dJ8Gvg71W7bg9yt8jjpmpESK-jKD7Wg@mail.gmail.com> <bf5a1810-8316-239c-0c5a-f85803048ab6@iki.fi> <CAD0rTC6H00cYrLU2zWa9jpexY9qH-07SHide1JdjN6Vpr4BHyg@mail.gmail.com>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset="UTF-8"
X-Trace	usenet.stanford.edu 1569070093 12339 209.51.188.17 (21 Sep 2019 12:48:13 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	bug-bash@gnu.org
To	Ilkka Virta <itvirta@iki.fi>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lHJD+95Y9sUHtL5hUcmarJXDaY8nMUtZOBcEfwKaEXs=; b=KbMHngJEBjz3jQtti+yaefB4w4eQNpDwGPol82liSlSF1ifP0nXEqTzpkXkflpwnFy g0SxrfPS8Y/JcDsfxA2bqpG9LAR0oMjroD3dhKn0WhmrpbRsmOUn/0XgJ2s9Q1SUxD/z Q9lgwsAcItVNJ3yVDrDvpQPY0rxXNN+pCVkAPwM+amh5Oq7JNG2zraOS28XVNJ9TQD50 JQ6zdf5YMNqAQSgnuY01c4tq3WKoNdJBhlIbw4VNoO3ia87g5foVuDlDR0q0IGC1rdQt 9vMnr99Q3BECjGWVzFj1WGJXZJxUe2WLcfdPIbZ1HEo1OzEkWsG4/8sCChWgYAl8sDM5 /pcA==
X-Google-DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lHJD+95Y9sUHtL5hUcmarJXDaY8nMUtZOBcEfwKaEXs=; b=TY/LhwBWNRneNGZVKoCvOSNBXjXSAUm/XMcSKzd0sohz1aDjTqp2zh/ezloFIr+fY3 SZpMBFsN1S8F25K2954m2vCjzlPK0YUpmKXziEcDY8aFtwihm1NAZ7En7eXCvdnzEw/5 D4BPb+cbDSs1TyrnhaREKIoW4lc3ekjE5DTkgkJ9/LHqE874qouoSJgSUFBAvRot1K73 dwSAKa2ZEXHNd4YDXhpI3pyDsJ9vikbpg809CU/G+k2nfR+pdrTSF+92mQ9yhSuAs22B 7M8SpO+qNN1a4YVXdzwsJh4YKXyEGzw3ztZ+4+mWt8aOqFxv4DWAEhnzCQW2JBmEJBPb LGGQ==
X-Gm-Message-State	APjAAAU7eHXsOFcYWpZSqLOCwY3IXhADNcX8/RMytVT743LFZfOMwtds HlvOCQy/6bA3B1b0IQV/hsaF7oUz0ELpLwJaV2Y=
X-Google-Smtp-Source	APXvYqxHs1Q5t54H3SmeNJRBSleYbIFhY5BnJR6igL6M6UEt9nOr2WkQp+l9HCxPrMjiOayXv0GWdYUjez2dGzZmQ7Q=
X-Received	by 2002:a37:5887:: with SMTP id m129mr8150823qkb.27.1569070086088; Sat, 21 Sep 2019 05:48:06 -0700 (PDT)
In-Reply-To	<bf5a1810-8316-239c-0c5a-f85803048ab6@iki.fi>
X-detected-operating-system	by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From	2607:f8b0:4864:20::733
X-Content-Filtered-By	Mailman/MimeDel 2.1.23
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.23
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<https://lists.gnu.org/archive/html/bug-bash>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID	<CAD0rTC6H00cYrLU2zWa9jpexY9qH-07SHide1JdjN6Vpr4BHyg@mail.gmail.com>
X-Mailman-Original-References	<CAD0rTC7W20s7-8np7Z+CmZQczTQ+LX=Y1x01gAenewrpiJS5jw@mail.gmail.com> <8e7c8ea4-2fdf-4809-0b50-ea1bfbbec165@case.edu> <CAD0rTC68qoXvCV9SLP1dJ8Gvg71W7bg9yt8jjpmpESK-jKD7Wg@mail.gmail.com> <bf5a1810-8316-239c-0c5a-f85803048ab6@iki.fi>
Xref	csiph.com gnu.bash.bug:15389

Show key headers only | View raw

Thanks. Have learnt a lot from your replies.

On Sat, Sep 21, 2019 at 5:34 PM Ilkka Virta <itvirta@iki.fi> wrote:

> On 21.9. 03:12, hk wrote:
> > Thanks for the reply. I was wrong in my report. It does match values like
> > aab and  aaaaaab  in its original form.
>
> In some systems, yes. (It does that on my Debian, but doesn't work at
> all on my Mac.)
>
> > It is syntatically correct as a regular expression.
>
> [[:space:]]*?(a)b  isn't a well-defined POSIX ERE:
>
>    9.4.6 EREs Matching Multiple Characters
>
>    The behavior of multiple adjacent duplication symbols ( '+', '*', '?',
>    and intervals) produces undefined results.
>
>
> https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/basedefs/V1_chap09.html
>
>
> --
> Ilkka Virta / itvirta@iki.fi
>

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Incorrect example for `[[` command. hk <hkadeveloper@gmail.com> - 2019-09-21 20:47 +0800

csiph-web