Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15420

Re: Documentation Bug Concerning Regular Expressions?

From Ilkka Virta <itvirta@iki.fi>
Newsgroups gnu.bash.bug
Subject Re: Documentation Bug Concerning Regular Expressions?
Date 2019-09-23 20:55 +0300
Message-ID <mailman.921.1569261353.2190.bug-bash@gnu.org> (permalink)
References <MWHPR2001MB1759D1C99BE7A8EEC24C6AA2C8850@MWHPR2001MB1759.namprd20.prod.outlook.com> <87e629fa-fe9b-f50d-4988-301445abc02b@iki.fi>

Show all headers | View raw


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

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


Thread

Re: Documentation Bug Concerning Regular Expressions? Ilkka Virta <itvirta@iki.fi> - 2019-09-23 20:55 +0300

csiph-web