How to represent multiple conditions in a shell if statement?

by

Classic technique (escape metacharacters):

if [ \( "$g" -eq 1 -a "$c" = "123" \) -o \( "$g" -eq 2 -a "$c" = "456" \) ]
then echo abc
else echo efg
fi

I’ve enclosed the references to $g in double quotes; that’s good practice, in general. Strictly, the parentheses aren’t needed because the precedence of -a and -o makes it correct even without them.

Note that the -a and -o operators are part of the POSIX specification for test, aka [, mainly for backwards compatibility (since they were a part of test in 7th Edition UNIX, for example), but they are explicitly marked as ‘obsolescent’ by POSIX. Bash (see conditional expressions) seems to preempt the classic and POSIX meanings for -a and -o with its own alternative operators that take arguments.

With some care, you can use the more modern [[ operator, but be aware that the versions in Bash and Korn Shell (for example) need not be identical.

for g in 1 2 3
do
    for c in 123 456 789
    do
        if [[ ( "$g" -eq 1 && "$c" = "123" ) || ( "$g" -eq 2 && "$c" = "456" ) ]]
        then echo "g = $g; c = $c; true"
        else echo "g = $g; c = $c; false"
        fi
    done
done

Example run, using Bash 3.2.57 on Mac OS X:

g = 1; c = 123; true
g = 1; c = 456; false
g = 1; c = 789; false
g = 2; c = 123; false
g = 2; c = 456; true
g = 2; c = 789; false
g = 3; c = 123; false
g = 3; c = 456; false
g = 3; c = 789; false

You don’t need to quote the variables in [[ as you do with [ because it is not a separate command in the same way that [ is.

Isn’t it a classic question?

I would have thought so. However, there is another alternative, namely:

if [ "$g" -eq 1 -a "$c" = "123" ] || [ "$g" -eq 2 -a "$c" = "456" ]
then echo abc
else echo efg
fi

Indeed, if you read the ‘portable shell’ guidelines for the autoconf tool or related packages, this notation — using ‘||‘ and ‘&&‘ — is what they recommend. I suppose you could even go so far as:

if [ "$g" -eq 1 ] && [ "$c" = "123" ]
then echo abc
elif [ "$g" -eq 2 ] && [ "$c" = "456" ]
then echo abc
else echo efg
fi

Where the actions are as trivial as echoing, this isn’t bad. When the action block to be repeated is multiple lines, the repetition is too painful and one of the earlier versions is preferable — or you need to wrap the actions into a function that is invoked in the different then blocks.

More Related Contents:

  1. What does 2>&1 mean here?
  2. How can I check if a directory exists in a Bash shell script?
  3. Difference between sh and Bash
  4. Pass commands as input to another command (su, ssh, sh, etc)
  5. Why do you need ./ (dot-slash) before executable or script name to run it in bash?
  6. Bash tool to get nth line from a file
  7. Bash command line and input limit
  8. Which characters need to be escaped when using Bash?
  9. “~/Desktop/test.txt: No such file or directory”
  10. Checking from shell script if a directory contains files
  11. How to suppress Terminated message after killing in bash?
  12. Delete files older than 10 days using shell script in Unix [duplicate]
  13. Copy folder recursively, excluding some folders
  14. Variable interpolation in the shell
  15. Piping tail output though grep twice
  16. How do I pause my shell script for a second before continuing?
  17. How to go to each directory and execute a command?
  18. Is there a way to make bash job control quiet?
  19. What does ” 2>&1 ” mean?
  20. Bash regex =~ operator
  21. How do I check if a directory exists or not in a Bash shell script?
  22. Print a file’s last modified date in Bash
  23. Validate date format in a shell script
  24. How can I convert tabs to spaces in every file of a directory?
  25. Convert Unix timestamp to a date string
  26. Using Bash to display a progress indicator (spinner) [duplicate]
  27. Extract version number from a string
  28. How to properly nest Bash backticks
  29. How to include nohup inside a bash script?
  30. Subtract two variables in Bash

Leave a Comment