Test if a command outputs an empty string

by

Previously, the question asked how to check whether there are files in a directory. The following code achieves that, but see rsp’s answer for a better solution.

Empty output

Commands don’t return values – they output them. You can capture this output by using command substitution; e.g. $(ls -A). You can test for a non-empty string in Bash like this:

if [[ $(ls -A) ]]; then
    echo "there are files"
else
    echo "no files found"
fi

Note that I’ve used -A rather than -a, since it omits the symbolic current (.) and parent (..) directory entries.

Note: As pointed out in the comments, command substitution doesn’t capture trailing newlines. Therefore, if the command outputs only newlines, the substitution will capture nothing and the test will return false. While very unlikely, this is possible in the above example, since a single newline is a valid filename! More information in this answer.

Exit code

If you want to check that the command completed successfully, you can inspect $?, which contains the exit code of the last command (zero for success, non-zero for failure). For example:

files=$(ls -A)
if [[ $? != 0 ]]; then
    echo "Command failed."
elif [[ $files ]]; then
    echo "Files found."
else
    echo "No files found."
fi

More info here.

More Related Contents:

  1. While loop stops reading after the first line in Bash
  2. How can I compare numbers in Bash?
  3. Pipe output and capture exit status in Bash
  4. Redirect stderr and stdout in Bash [duplicate]
  5. Why equal to operator does not work if it is surrounded by space?
  6. Which characters need to be escaped when using Bash?
  7. “~/Desktop/test.txt: No such file or directory”
  8. Capturing Groups From a Grep RegEx
  9. Why does “local” sweep the return code of a command?
  10. bash : Illegal number
  11. Batch renaming files with Bash
  12. Shell redirection i/o order
  13. How to generate random number in Bash?
  14. “Invalid Arithmetic Operator” when doing floating-point math in bash
  15. Using sed to mass rename files
  16. Colorized grep — viewing the entire file with highlighted matches
  17. How to pass in password to pg_dump?
  18. Select random lines from a file
  19. Variables getting reset after the while read loop that reads from a pipeline
  20. Hexadecimal To Decimal in Shell Script
  21. LINES and COLUMNS environmental variables lost in a script
  22. Should I use a Shebang with Bash scripts?
  23. How to reset COMP_WORDBREAKS without affecting other completion script?
  24. How do file descriptors work?
  25. Execute a shell function with timeout
  26. Convert Unix timestamp to a date string
  27. Using Bash to display a progress indicator (spinner) [duplicate]
  28. When does command substitution spawn more subshells than the same commands in isolation?
  29. How to properly nest Bash backticks
  30. Subtract two variables in Bash

Leave a Comment