|
Size: 1160
Comment: link to #50
|
Size: 1367
Comment: first-line
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Anchor(faq66)]] | <<Anchor(faq66)>> |
| Line 3: | Line 3: |
| The portable solution uses `case`: | |
| Line 4: | Line 5: |
| Here's a portable solution: | |
| Line 27: | Line 27: |
| Please also note that the regexp does not need to be quoted in the 3.2 revisions where it works. --["redondos"] | Please also note that the regexp does not need to be quoted in the 3.2 revisions where it works. --[[redondos]] |
| Line 29: | Line 29: |
| Normally I would never advocate [:BashFAQ/050:sticking code into a variable] and attempting to use it -- lots of people have ''enormous'' trouble because they try to do that. In the case of `=~`, though, it seems to be required. Personally, I'd just stick with the `case`. --GreyCat | Normally I would never advocate [[BashFAQ/050|sticking code into a variable]] and attempting to use it -- lots of people have ''enormous'' trouble because they try to do that. In the case of `=~`, though, it seems to be required. Personally, I'd just stick with the `case`. --GreyCat The regexp works as long as it is quoted with bash version ''3.00.15(1)-release'' on CentOS4/RHEL4. I didn't bother checking whether bash is a patched version or not in CentOS4/RHEL4. --ellingsw |
I want to check if [[ $var == foo || $var == bar || $var == more ]] without repeating $var n times.
The portable solution uses case:
case $var in
foo|bar|more) ... ;;
esacAnd here's one that uses =~ (which requires bash 3.0 or higher):
regex='^(foo|bar|more)$'
if [[ $var =~ $regex ]]; then
...
fiThis one only works in bash 3.1 and some 3.2 revisions (it is untested in 3.0):
if [[ $var =~ '^(foo|bar|more)$' ]]; then
...
fiThe =~ operator behavior changes drastically between 3.1 and 3.2, so be careful with it. The above expression is tested to work in bash 3.1 and 3.2.{13,15,17}; and it doesn't work in 3.2.0. Please also note that the regexp does not need to be quoted in the 3.2 revisions where it works. --redondos
Normally I would never advocate sticking code into a variable and attempting to use it -- lots of people have enormous trouble because they try to do that. In the case of =~, though, it seems to be required. Personally, I'd just stick with the case. --GreyCat
The regexp works as long as it is quoted with bash version 3.00.15(1)-release on CentOS4/RHEL4. I didn't bother checking whether bash is a patched version or not in CentOS4/RHEL4. --ellingsw