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 matching, as with the other pattern-matching > operators." > > between 3.1->3.2 complete breaks my script.
Yeah, I had the same problem. Very annoying. > 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? I am pretty sure there is none. The suggested workaround is to put the string to be matched into a variable: <http://bashcurescancer.com/bash_faq_version_336_for_bash_version_32#SUB-E14> Wonko -- [EMAIL PROTECTED] mailing list
