Differences between revisions 3 and 4
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 4 as of 2007-05-24 15:23:46
Size: 813
Editor: GreyCat
Comment: a workaround
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
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): And here's one that uses `=~` (which requires bash 3.0 or higher):
{{{
   regex='^(foo|bar|more)$'
   if [[ $var =~ $regex ]]; then
      ...
   fi
}}}

This one '''only works in bash 3.1''', not in bash 3.2 (and is untested in 3.0):
Line 18: Line 26:
I'd just stick with the `case`, myself. --GreyCat 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

Anchor(faq66)

I want to check if [[ $var == foo || $var == bar || $var == more ]] without repeating $var n times.

Here's a portable solution:

   case $var in
      foo|bar|more) ... ;;
   esac

And here's one that uses =~ (which requires bash 3.0 or higher):

   regex='^(foo|bar|more)$'
   if [[ $var =~ $regex ]]; then
      ...
   fi

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

BashFAQ/066 (last edited 2015-06-20 07:58:04 by ormaaj)