Bash If-statement to check If string is equal to one of several string literals [duplicate]

by

The conventional approach, compatible with POSIX sh rather than leveraging bashisms, is to use the case statement:

case $level in
   -|0|+)
     echo "Got it!" ;;
   *)
     echo "Not a valid value" ;;
esac

That said, if you wanted to use test, you could do that too:

if [ "$LEVEL" != "-" ] && [ "$LEVEL" != "0" ] && [ "$LEVEL" != "+" ]; then
  ...
fi

!= is the negating string comparison operator, and = (not ==) is the POSIX-compatible positive-matching one. (Bash extends POSIX to support == in test, but making a habit of using this extension will get you into trouble if you try to write code for a pure POSIX shell later).

Below here, there be bashisms! (Above is POSIX compliant).

In a comment, a follow-up question was asked, in terms of whether the set of possible characters could be read from a variable. In general, yes, though there are some caveats:

# no spaces in possible_levels, as we're using it to form a pattern
possible_levels="-0+"
possible_levels_pattern="[${possible_levels}]"
if [[ $value = $possible_levels_pattern ]]; then
  echo "value contains a valid level"
fi

…As an even shorter approach that allows your input string to be used unmodified, and is almost correct:

# caveat: will say some incorrect strings, like "- 0" or "0 +", are valid levels
possible_levels=" - 0 +"
check_level() {
  [[ " $possible_levels " = *" $1 "* ]] && echo "Value is a valid level"
}

…or, as yet another implementation (verbose, but correct in the particulars):

possible_levels=" - 0 +"
read -a possible_levels_array <<<"$possible_levels"
check_level() {
  local possible_level
  local value=$1
  for possible_level in "${possible_levels_array[@]}"; do
    [[ $value = "$possible_level" ]] && return 0
  done
  return 1
}

if check_level "$value"; then
  echo "$value is a valid level"
else
  echo "$value is not a valid level"
fi

Obviously, this is a lot of work, and in general, just hardcoding the comparisons when appropriate (and possible without a loss of safety) will save you trouble over trying to make things more generic than they truly need to be.

Now, if we could pass in the variable as an associative array, without needing to support the silly space-separated-list thing, that makes it much shorter:

declare -A possible_levels=( [-]=1 [+]=1 [0]=1 )
if [[ ${possible_levels[$value]} ]]; then
  echo "valid level"
else
  echo "invalid level"
fi

More Related Contents:

  1. Erroe in script
  2. How to pass a variable containing slashes to sed
  3. Fast way of finding lines in one file that are not in another?
  4. sudo echo “something” >> /etc/privilegedFile doesn’t work [duplicate]
  5. How to detect the OS from a Bash script?
  6. While-loop subshell dilemma in Bash
  7. Variables in bash seq replacement ({1..10}) [duplicate]
  8. ffmpeg in a bash pipe
  9. Check existence of input argument in a Bash shell script
  10. How to simulate the environment cron executes a script with?
  11. How do I grab an INI value within a shell script?
  12. How to make the ‘cut’ command treat same sequental delimiters as one?
  13. How to add to the end of lines containing a pattern with sed or awk?
  14. How to increment a date in a Bash script
  15. Running multiple commands in one line in shell
  16. Why source command doesn’t work with process substitution in bash 3.2?
  17. error while running “source .vimrc”
  18. Variable variable assignment error -“command not found”
  19. find files older than X days in bash and delete
  20. How to Batch Rename Files in a macOS Terminal?
  21. bash background process modify global variable
  22. BASH Syntax error near unexpected token ‘done’ [duplicate]
  23. In what order should I send signals to gracefully shutdown processes?
  24. Bash regex =~ operator
  25. How can I use long options with the Bash getopts builtin?
  26. How to use `while read` (Bash) to read the last line in a file if there’s no newline at the end of the file?
  27. Parse HTML using shell
  28. How to send a signal SIGINT from script to script?
  29. Getting a ‘source: not found’ error when using source in a bash script
  30. docker entrypoint running bash script gets “permission denied”

Leave a Comment