Re: extglob

On Sat, May 16, 2009 at 2:44 AM, Chris F.A. Johnson wrote: > >   Am I missing something, or are these extended globbing patterns >   equivalent to a plain asterisk? > > ?(pattern-list) Matches zero or one occurrence of the given patterns > *(pattern-list) Matches zero or more occurrences of the gi

extglob

Am I missing something, or are these extended globbing patterns equivalent to a plain asterisk? ?(pattern-list) Matches zero or one occurrence of the given patterns *(pattern-list) Matches zero or more occurrences of the given patterns -- Chris F.A. Johnson, webmaster

Re: --rcfile still opening the SYS_BASHRC

2009/5/15 Chet Ramey : > Lluís Batlle wrote: >> Hello, >> >> I have a problem in bash (3.2 and 4). I have it compiled with >> "-DSYS_BASHRC=/etc/bashrc", and since some time ago I could use "bash >> --rcfile ~/.myrc" to skip the parsing of /etc/bashrc. >> >> I can't recall what was the compile conf

Re: bash 4.0p17 problem with CTRL+C

Alan Hourihane wrote: > On Fri, 2009-05-15 at 13:19 +0200, Roman Rakus wrote: >> On 05/15/2009 12:02 PM, Alan Hourihane wrote: >>> Hi all, >>> >>> I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any >>> effect until I hit. >>> >>> bash 3.2 worked perfectly, so I'm a little unsu

Re: --rcfile still opening the SYS_BASHRC

Lluís Batlle wrote: > Hello, > > I have a problem in bash (3.2 and 4). I have it compiled with > "-DSYS_BASHRC=/etc/bashrc", and since some time ago I could use "bash > --rcfile ~/.myrc" to skip the parsing of /etc/bashrc. > > I can't recall what was the compile configuration of that bash where >

Re: bash 4.0p17 problem with CTRL+C

On Fri, 2009-05-15 at 13:19 +0200, Roman Rakus wrote: > On 05/15/2009 12:02 PM, Alan Hourihane wrote: > > Hi all, > > > > I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any > > effect until I hit. > > > > bash 3.2 worked perfectly, so I'm a little unsure what's caused this. >

Re: bash 4.0p17 problem with CTRL+C

On 05/15/2009 12:02 PM, Alan Hourihane wrote: Hi all, I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any effect until I hit. bash 3.2 worked perfectly, so I'm a little unsure what's caused this. Can anyone point me at the code which handles this and I can take a closer lo

bash 4.0p17 problem with CTRL+C

Hi all, I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any effect until I hit . bash 3.2 worked perfectly, so I'm a little unsure what's caused this. Can anyone point me at the code which handles this and I can take a closer look ? Thanks, Alan.