|
Size: 813
Comment: a workaround
|
Size: 487
Comment: rm old comments, rm regex examples because they're stupid and pointless, add category
|
| 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 6: | Line 6: |
| case $var in | # Bourne case "$var" in |
| Line 11: | Line 12: |
| And here's one that uses `=~` (which requires bash 3.0 or higher): | In Bash and ksh, [[glob|Extended globs]] can also do this within a `[[` command: |
| Line 13: | Line 14: |
| regex='^(foo|bar|more)$' if [[ $var =~ $regex ]]; then |
# bash/ksh -- ksh does not need the shopt shopt -s extglob if [[ $var = @(foo|bar|more) ]]; then |
| Line 19: | Line 21: |
| This one '''only works in bash 3.1''', not in bash 3.2 (and is untested in 3.0): {{{ if [[ $var =~ '^(foo|bar|more)$' ]]; then ... fi }}} 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 |
---- CategoryShell |
I want to check if [[ $var == foo || $var == bar || $var == more ]] without repeating $var n times.
The portable solution uses case:
# Bourne
case "$var" in
foo|bar|more) ... ;;
esacIn Bash and ksh, Extended globs can also do this within a [[ command:
# bash/ksh -- ksh does not need the shopt
shopt -s extglob
if [[ $var = @(foo|bar|more) ]]; then
...
fi