Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Ilkka Virta <itvirta@iki.fi>
Newsgroups: gnu.bash.bug
Subject: Re: Documentation Bug Concerning Regular Expressions?
Date: Mon, 23 Sep 2019 20:55:41 +0300
Lines: 16
Approved: bug-bash@gnu.org
Message-ID: <mailman.921.1569261353.2190.bug-bash@gnu.org>
References: <MWHPR2001MB1759D1C99BE7A8EEC24C6AA2C8850@MWHPR2001MB1759.namprd20.prod.outlook.com> <87e629fa-fe9b-f50d-4988-301445abc02b@iki.fi>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: usenet.stanford.edu 1569261354 2336 209.51.188.17 (23 Sep 2019 17:55:54 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: "bug-bash@gnu.org" <bug-bash@gnu.org>
To: "Hults, Josh" <JHults@Serigraph.com>
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: <MWHPR2001MB1759D1C99BE7A8EEC24C6AA2C8850@MWHPR2001MB1759.namprd20.prod.outlook.com>
Content-Language: en-US
X-SASI-RCODE: 200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; h=subject:to:references:cc:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=smtp; bh=Rkox/Dg4PuwhxqeO3hMTn7FsZXoLaEdjsJ9u32vozl4=; b=q3R8ysCk5z/T4HjXVP/KnJJDcmIXZuX2KzKmX+OmjQuAPkayvcmQj9/p2oDVxEpzCvy3G1xpme4/4yW4eikVEUVqcOcrllzYk+X5ClNvEQ2lIX+Zqo/jIPOb1k+wuRaSBY+vkfLKdcA9jDM8dX30JWTExe++1SQP6s5aROZnqksOVqoGzRZFwmeWKtwr4oPs4DoJhUaOmobWxlCQ3ZXZGJnUpuqN7hKl2oNGkKHcnv+R3loqycU/1nah/P3r2x9RTH0Rs+gFJWWqWhzX/0cGOz03Wah5w4CQANQmwF0VjlRK45mnBTQHVsjWG8g+SjcKQybEDfqAslFGCxZeuKYg+Q==
X-detected-operating-system: by eggs.gnu.org: FreeBSD 8.x
X-Received-From: 157.24.2.104
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: <87e629fa-fe9b-f50d-4988-301445abc02b@iki.fi>
X-Mailman-Original-References: <MWHPR2001MB1759D1C99BE7A8EEC24C6AA2C8850@MWHPR2001MB1759.namprd20.prod.outlook.com>
Xref: csiph.com gnu.bash.bug:15420

On 23.9. 19:56, Hults, Josh wrote:
> Hello Bash Maintainers,
> 
> In the currently posted version of the Bash documentation, there is a section regarding Conditional Constructs (3.2.4.2, https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Conditional-Constructs).  Within that section is a portion discussing the [[ ... ]] operator, and within that portion is a discussion of the "=~" regex operator.
> 
> The example given of a regex pattern is:  [[ $line =~ [[:space:]]*?(a)b ]].  (This example is referenced twice)

Yes, that exact example has been discussed for a couple of days, 
starting at this message from last Friday:

https://lists.gnu.org/archive/html/bug-bash/2019-09/msg00042.html


-- 
Ilkka Virta / itvirta@iki.fi