What is the purpose of the : (colon) GNU Bash builtin?

by

Historically, Bourne shells didn’t have true and false as built-in commands. true was instead simply aliased to :, and false to something like let 0.

: is slightly better than true for portability to ancient Bourne-derived shells. As a simple example, consider having neither the ! pipeline operator nor the || list operator (as was the case for some ancient Bourne shells). This leaves the else clause of the if statement as the only means for branching based on exit status:

if command; then :; else ...; fi

Since if requires a non-empty then clause and comments don’t count as non-empty, : serves as a no-op.

Nowadays (that is: in a modern context) you can usually use either : or true. Both are specified by POSIX, and some find true easier to read. However there is one interesting difference: : is a so-called POSIX special built-in, whereas true is a regular built-in.

  • Special built-ins are required to be built into the shell; Regular built-ins are only “typically” built in, but it isn’t strictly guaranteed. There usually shouldn’t be a regular program named : with the function of true in PATH of most systems.

  • Probably the most crucial difference is that with special built-ins, any variable set by the built-in – even in the environment during simple command evaluation – persists after the command completes, as demonstrated here using ksh93:

    $ unset x; ( x=hi :; echo "$x" )
hi
$ ( x=hi true; echo "$x" )

$

    Note that Zsh ignores this requirement, as does GNU Bash except when operating in POSIX compatibility mode, but all other major “POSIX sh derived” shells observe this including dash, ksh93, and mksh.

  • Another difference is that regular built-ins must be compatible with exec – demonstrated here using Bash:

    $ ( exec : )
-bash: exec: :: not found
$ ( exec true )
$

  • POSIX also explicitly notes that : may be faster than true, though this is of course an implementation-specific detail.

More Related Contents:

  1. What does “<
  2. What does 2>&1 mean here?
  3. How to reload .bashrc settings without logging out and back in again?
  4. How do I iterate over a range of numbers defined by variables in Bash?
  5. Why would a correct shell script give a wrapped/truncated/corrupted error message? [duplicate]
  6. When do we need curly braces around shell variables?
  7. Multi-dimensional arrays in Bash
  8. How do I check if a directory exists in a Bash shell script?
  9. Capture stdout and stderr into different variables
  10. How to determine the current interactive shell that I’m in (command-line)
  11. Associative arrays in Shell scripts
  12. How to get the part of a file after the first line that matches a regular expression
  13. Open and write data to text file using Bash?
  14. bash set -e and i=0;let i++ do not agree
  15. How do I echo stars (*) when reading password with `read`?
  16. Why is this bash prompt acting strangely/disappearing, and how do I fix it (OS X)?
  17. Why is “[[ 10 < 2 ]]" true when comparing numbers in bash? [duplicate]
  18. Bash: Copy named files recursively, preserving folder structure
  19. How to go to each directory and execute a command?
  20. Read a variable in bash with a default value
  21. Relative paths based on file location instead of current working directory [duplicate]
  22. Counting lines or enumerating line numbers so I can loop over them – why is this an anti-pattern?
  23. What does “export” do in shell programming? [duplicate]
  24. What is the most elegant way to remove a path from the $PATH variable in Bash?
  25. pipe stdout and stderr to two different processes in shell script?
  26. How can I convert tabs to spaces in every file of a directory?
  27. How to match a single quote in sed
  28. -bash: __git_ps1: command not found
  29. Use GNU find to show only the leaf directories
  30. Get the name of the caller script in bash script

Leave a Comment