-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Willie Wong wrote:
> On Sat, Nov 10, 2007 at 11:13:10AM +0200, Penguin Lover Etaoin
> Shrdlu squawked:
>>> The question:
>>>
>>> Is there a switch that I can use to make bash run in some sort
>>> of compatibility mode for the string comparison? I.e, c
On Sat, Nov 10, 2007 at 01:46:33PM +0100, Penguin Lover Alex Schuster squawked:
> [EMAIL PROTECTED] writes:
> > I have the same problem and I was trying to solve it few weeks ago,
> > after almost two weeks of searching and compiling I substituted =~ with
> > expr:
> >
> > - orig use with ~= :
> >
On Sat, Nov 10, 2007 at 11:13:10AM +0200, Penguin Lover Etaoin Shrdlu squawked:
> > The question:
> >
> > Is there a switch that I can use to make bash run in some sort of
> > compatibility mode for the string comparison? I.e, can I somehow
> > force bash (in the script) to behave like before
[EMAIL PROTECTED] writes:
> I have the same problem and I was trying to solve it few weeks ago,
> after almost two weeks of searching and compiling I substituted =~ with
> expr:
>
> - orig use with ~= :
> # if [[ "test" =~ ".*" ]]; then echo "ok"; fi
>
> - alternative use with expr :
> # export TE
On Friday 9 November 2007, Willie Wong wrote:
> The question:
>
> Is there a switch that I can use to make bash run in some sort of
> compatibility mode for the string comparison? I.e, can I somehow
> force bash (in the script) to behave like before?
Low-tech solution: can't you just instal
va --------
> Od: Alex Schuster <[EMAIL PROTECTED]>
> Předmět: Re: [gentoo-user] Bash 3.2/3.1 compatibility?
> Datum: 10.11.2007 04:14:19
>
> Willie Wong writes:
>
> > The situation:
> > I have some bash scripts
Willie Wong writes:
> The situation:
> I have some bash scripts written. The scripts contains a lot of
> string comparisons. Perhaps my code was buggy before, perhaps it was
> not, but the change
>
> "Quoting the string argument to the [[ command's =~ operator now
> forces string ma
Hi list,
The situation:
I have some bash scripts written. The scripts contains a lot of
string comparisons. Perhaps my code was buggy before, perhaps it was
not, but the change
"Quoting the string argument to the [[ command's =~ operator now
forces string matching, as with the oth
8 matches
Mail list logo
