Differences between revisions 3 and 11 (spanning 8 versions)
Revision 3 as of 2007-05-24 15:17:19
Size: 496
Editor: GreyCat
Comment: =~ example was wrong. very wrong. and is still mostly wrong.
Revision 11 as of 2012-04-29 23:44:04
Size: 487
Editor: ormaaj
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). This '''only works in bash 3.1''', not in bash 3.2 (and is untested in 3.0): In Bash and ksh, [[glob|Extended globs]] can also do this within a `[[` command:
Line 13: Line 14:
   if [[ $var =~ '^(foo|bar|more)$' ]]; then    # bash/ksh -- ksh does not need the shopt
   shopt -s extglob
if [[ $var = @(foo|bar|more) ]]; then
Line 18: Line 21:
I'd just stick with the `case`, myself. --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) ... ;;
   esac

In 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


CategoryShell

BashFAQ/066 (last edited 2022-11-23 19:29:49 by GreyCat)