Today we are going to delve into the fascinating world of Echo (command). This topic has been the object of study and interest for many years, and its importance is undeniable in different areas of daily life. Echo (command) has impacted history, science, culture, technology and society in general. Through this article, we will explore different aspects of Echo (command), from its origin and evolution to its influence on the world today. We will discover fascinating facts, curiosities and relevant information that will allow us to better understand the importance of Echo (command) in our daily lives.
![]() The echo command on Unix | |
Original author(s) | Douglas McIlroy (AT&T Bell Laboratories) |
---|---|
Developer(s) | Various open-source and commercial developers |
Operating system | Multics, Unix, Unix-like, V, Plan 9, Inferno, FLEX, TRIPOS, AmigaDOS, Z80-RIO, OS-9, DOS, MSX-DOS, Panos, FlexOS, SISNE plus, OS/2, Windows, ReactOS, MPE/iX, KolibriOS, SymbOS |
Platform | Cross-platform |
Type | Command |
echo
is shell command that writes input text to standard output. It is available in many operating system and shells. It is often used in a shell script to log status, provide feedback to the user and for debugging. For an interactive session, output by default displays on the terminal screen, but output can be re-directed to a file or piped to another process.[1]
Many shells implement echo
as a builtin command rather than an external application as are many other commands.
Multiple, incompatible implementations of echo
exist in different shells. Some expand escape sequences by default; some do not; some accept options; some do not. The POSIX specification[2] leaves the behavior unspecified if the first argument is -n
or any argument contains 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, echo
is considered a non-portable command[3] and the printf
command (introduced in Ninth Edition Unix) is preferred instead.
The command is available the following shells or at least one shell of a listed operating system:
echo
began within Multics. After it was programmed in C by Doug McIlroy as a "finger exercise" and proved to be useful, it 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).[17]
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.[18]
Eighth Edition Unix echo
only did the escape expansion when passed a -e
option,[19] and that behaviour was copied by a few other implementations such as the builtin echo
command of Bash or zsh and GNU echo
.
On MS-DOS, the command is available in versions 2 and later.[20]
C:\>echo Hello world
Hello world
Using ANSI escape code SGR sequences, compatible terminals can print out colored text.
Using a UNIX System III-style implementation:
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}"