echo (command)

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

echo command
echo command
Operating systemTRIPOS, DOS, FlexOS, OS/2, Microsoft Windows, ReactOS, MPE/iX, KolibriOS, SymbOS, Unix, Unix-like, OS-9

In computing, echo is a command in TRIPOS[1], DOS, FlexOS[2], OS/2, Microsoft Windows, ReactOS, MPE/iX[3], KolibriOS[4], Unix and Unix-like operating systems that outputs the strings it is being passed as arguments. It is a command typically used in shell scripts and batch files to output status text to the screen[5] or a computer file, or as a source part of a pipeline.

Many shells, including all Bourne-like (such as Bash[6] or zsh[7]) and Csh-like shells as well as COMMAND.COM and cmd.exe implement echo as a builtin command.

The command is also available in the EFI shell.[8]


echo began within Multics, and became part of Version 2 Unix. echo -n in Version 7 replaced prompt, (which behaved like echo but without terminating its output with a line delimiter).[9]

On PWB/UNIX and later Unix System III, echo started expanding C escape sequences such as \n with the notable difference that octal escape sequences were expressed as \0ooo instead of \ooo in C.[10]

Eighth Edition Unix echo only did the escape expansion when passed a -e option,[11] and that behaviour was copied by a few other implementations such as the builtin echo command of Bash or zsh and GNU echo.

Nowadays, several incompatible implementations of echo exist on different operating systems (often several on the same system), some of them expanding escape sequences by default, some of them not, some of them accepting options (the list of which varying with implementations), some of them not.

The POSIX Specification of echo[12] leaves the behaviour unspecified if the first argument is -n or any argument contain backslash characters while the Unix specification (XSI option in POSIX) mandates the expansion of (some) sequences and does not allow any option processing. In practice, many echo implementations are not compliant in the default environment.

Because of these variations in behaviour, echo is considered a non-portable command on Unix-like systems[13] and the printf command (where available, introduced by Ninth Edition Unix) is preferred instead.

Usage example[edit]

goto crash

Using ANSI escape code SGR sequences, compatible terminals can print out colored text.

Using a System III-style implementation of echo):

BGRED=`echo "\033[41m"`
FGBLUE=`echo "\033[35m"`
BGGREEN=`echo "\033[42m"`

NORMAL=`echo "\033[m"`

Or a Unix Version 8-style implementation (such as Bash when not in Unix-conformance mode):

BGRED=`echo -e "\033[41m"`
FGBLUE=`echo -e "\033[35m"`
BGGREEN=`echo -e "\033[42m"`

NORMAL=`echo -e "\033[m"`

and after:

echo "${FGBLUE} Text in blue ${NORMAL}"
echo "Text normal"
echo "${BGRED} Background in red"
echo "${BGGREEN} Background in Green and back to Normal ${NORMAL}"

Portably with printf:

BGRED=`printf '\33[41m'`
NORMAL=`printf '\33[m'`
printf '%s\n' "${BGRED}Text on red background${NORMAL}"

See also[edit]


  1. ^
  2. ^
  3. ^ MPE/iX Command Reference Manual
  4. ^
  5. ^
  6. ^
  7. ^
  8. ^ "EFI Shells and Scripting". Intel. Retrieved 2013-09-25.
  9. ^ McIlroy, M. D. (1987). A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 (PDF) (Technical report). CSTR. Bell Labs. 139.
  10. ^ Mascheck, Sven. "echo and printf behaviour". Retrieved 24 July 2016.
  11. ^ "8th Edition Unix echo man page". Retrieved 24 July 2016.
  12. ^ echo: write arguments to standard output – Commands & Utilities Reference, The Single UNIX Specification, Issue 7 from The Open Group
  13. ^ "Autoconf documentation on echo portability". Free Software Foundation. Retrieved 24 July 2016.

External links[edit]