2 .\" Copyright 1989 AT&T
3 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
4 .\" Portions Copyright (c) 1992, X/Open Company Limited All Rights Reserved
5 .\" Portions Copyright (c) 1982-2007 AT&T Knowledge Ventures
6 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
7 .\" http://www.opengroup.org/bookstore/.
8 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
9 .\" This notice shall appear on any product containing this material.
10 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
11 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
12 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
13 .TH ECHO 1 "Apr 14, 2016"
15 echo \- echo arguments
19 \fB/usr/bin/echo\fR [\fIstring\fR]...
24 The \fBecho\fR utility writes its arguments, separated by BLANKs and terminated
25 by a NEWLINE, to the standard output. If there are no arguments, only the
26 NEWLINE character is written.
29 \fBecho\fR is useful for producing diagnostics in command files, for sending
30 known data into a pipe, and for displaying the contents of environment
34 The C shell, the Korn shell, and the Bourne shell all have \fBecho\fR built-in
35 commands, which, by default, is invoked if the user calls \fBecho\fR without a
36 full pathname. See \fBshell_builtins\fR(1). \fBsh\fR's \fBecho\fR, \fBksh\fR's
37 \fBecho\fR, \fBksh93\fR's \fBecho\fR, and \fB/usr/bin/echo\fR understand the
38 back-slashed escape characters, except that \fBsh\fR's \fBecho\fR does not
39 understand \fB\ea\fR as the alert character. In addition, \fBksh\fR's and
40 \fBksh93\fR's \fBecho\fR does not have an \fB-n\fR option.
41 \fBcsh\fR's \fBecho\fR and \fB/usr/ucb/echo\fR, on the other hand, have an
42 \fB-n\fR option, but do not understand the back-slashed escape characters.
43 \fBsh\fR and \fBksh\fR determine whether \fB/usr/ucb/echo\fR is found first in
44 the \fBPATH\fR and, if so, they adapt the behavior of the \fBecho\fR builtin to
45 match \fB/usr/ucb/echo\fR.
48 The following operand is supported:
55 A string to be written to standard output. If any operand is "\fB-n\fR", it is
56 treated as a string, not an option. The following character sequences is
57 recognized within any of the arguments:
82 Print line without new-line. All characters following the \fB\ec\fR in the
143 \fB\fB\e0\fR\fIn\fR\fR
146 Where \fIn\fR is the 8-bit character whose \fBASCII\fR code is the 1-, 2- or
147 3-digit octal number representing that character.
154 Portable applications should not use \fB-n\fR (as the first argument) or escape
158 The \fBprintf\fR(1) utility can be used portably to emulate any of the
159 traditional behaviors of the \fBecho\fR utility as follows:
164 The Solaris 2.6 operating environment or compatible version's
165 \fB/usr/bin/echo\fR is equivalent to:
169 \fBprintf "%b\en" "$*"\fR
179 The \fB/usr/ucb/echo\fR is equivalent to:
202 New applications are encouraged to use \fBprintf\fR instead of \fBecho\fR.
205 \fBExample 1 \fRFinding how far below root your current directory is located
208 You can use \fBecho\fR to determine how many subdirectories below the root
209 directory (\fB/\fR) is your current directory, as follows:
215 Echo your current-working-directory's full pathname.
221 Pipe the output through \fBtr\fR to translate the path's embedded
222 slash-characters into space-characters.
228 Pipe that output through \fBwc\fR \fB-w\fR for a count of the names in your
233 example% \fB/usr/bin/echo $PWD | tr '/' ' ' | wc -w\fR
241 See \fBtr\fR(1) and \fBwc\fR(1) for their functionality.
245 Below are the different flavors for echoing a string without a NEWLINE:
247 \fBExample 2 \fR/usr/bin/echo
251 example% \fB/usr/bin/echo "$USER's current directory is $PWD\ec"\fR
257 \fBExample 3 \fRsh/ksh shells
261 example$ \fBecho "$USER's current directory is $PWD\ec"\fR
267 \fBExample 4 \fRcsh shell
271 example% \fBecho -n "$USER's current directory is $PWD"\fR
277 \fBExample 5 \fR/usr/ucb/echo
281 example% \fB/usr/ucb/echo -n "$USER's current directory is $PWD"\fR
286 .SH ENVIRONMENT VARIABLES
288 See \fBenviron\fR(5) for descriptions of the following environment variables
289 that affect the execution of \fBecho\fR: \fBLANG\fR, \fBLC_ALL\fR,
290 \fBLC_CTYPE\fR, \fBLC_MESSAGES\fR, and \fBNLSPATH\fR.
294 The following error values are returned:
301 Successful completion.
315 See \fBattributes\fR(5) for descriptions of the following attributes:
323 ATTRIBUTE TYPE ATTRIBUTE VALUE
327 Interface Stability Committed
329 Standard See \fBstandards\fR(5).
334 \fBksh93\fR(1), \fBprintf\fR(1), \fBshell_builtins\fR(1), \fBtr\fR(1),
335 \fBwc\fR(1), \fBecho\fR(1B), \fBascii\fR(5), \fBattributes\fR(5),
336 \fBenviron\fR(5), \fBstandards\fR(5)
339 When representing an 8-bit character by using the escape convention
340 \fB\e0\fR\fIn\fR, the \fIn\fR must \fBalways\fR be preceded by the digit zero
344 For example, typing: \fBecho 'WARNING:\e\|07'\fR prints the phrase
345 \fBWARNING:\fR and sounds the "bell" on your terminal. The use of single (or
346 double) quotes (or two backslashes) is required to protect the "\|\e" that
350 Following the \fB\e0\fR, up to three digits are used in constructing the octal
351 output character. If, following the \fB\e0\fR\fIn\fR, you want to echo
352 additional digits that are not part of the octal representation, you must use
353 the full 3-digit \fIn\fR. For example, if you want to echo "ESC 7" you must use
354 the three digits "033" rather than just the two digits "33" after the
359 2 digits Incorrect: echo "\e0337" | od -xc
362 3 digits Correct: echo "\e00337" | od -xc
363 produces: lb37 0a00 (hex)
371 For the octal equivalents of each character, see \fBascii\fR(5).