Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-17 Thread Chet Ramey
On 1/17/19 1:53 AM, kevin wrote: > >    Since *[[* isn't a normal command (like [ is), but a /shell >    keyword/, *it has special magical powers*. *It parses its arguments >    before they are expanded by Bash and does the expansion itself*, >    taking the result as a single argument, even if t

Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-17 Thread Greg Wooledge
On Thu, Jan 17, 2019 at 07:53:09AM +0100, kevin wrote: > I looked at Greg Wooledge's site > : > > >Since *[[* isn't a normal command (like [ is), but a /shell >keyword/, *it has spe

Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-16 Thread kevin
Le 17/01/2019 à 07:53, kevin a écrit : Le 12/01/2019 à 23:27, Chet Ramey a écrit : On 1/12/19 1:14 AM, kevin wrote: Moreover, the explanation in the Bash FAQ is unclear; it lacks examples to know when "an interference" occurred. What is "an interference"? Look at the following answer to ge

Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-16 Thread kevin
Le 12/01/2019 à 23:27, Chet Ramey a écrit : On 1/12/19 1:14 AM, kevin wrote: Moreover, the explanation in the Bash FAQ is unclear; it lacks examples to know when "an interference" occurred. What is "an interference"? Look at the following answer to get an overview of the issue: https://stac

Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-12 Thread Chet Ramey
On 1/12/19 1:14 AM, kevin wrote: >>> Moreover, the explanation in the Bash FAQ is unclear; it lacks examples to >>> know when "an interference" occurred. >> What is "an interference"? >> >> >>> Look at the following answer to get an overview of the issue: >>> https://stackoverflow.com/a/12696899 >

Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-09 Thread Chet Ramey
On 1/9/19 2:27 PM, kevin wrote: > My message was poorly formatted (I lack of experience) and consequently you > misunderstood it. > The shell operation is unusual when a regular expression appears inside a > conditional expression. Indeed, neither the Bash man page or the Bash > Reference Manual in

Re: [DOC] Incomplete explanation about the regex =~ operator

2019-01-08 Thread Greg Wooledge
On Tue, Jan 08, 2019 at 10:47:21AM +, gilaro wrote: > See also: Does bash support word boundary regular expressions? Short answer: No. Long answer: Bash's =~ operator uses Extended Regular Expressions (ERE), as implemented by your system's C library's regular expression engine. Your system m