1 .\" Copyright (c) 1989, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" the Institute of Electrical and Electronics Engineers, Inc.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 4. Neither the name of the University nor the names of its contributors
16 .\" may be used to endorse or promote products derived from this software
17 .\" without specific prior written permission.
19 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
23 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
24 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
25 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
28 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
31 .\" @(#)printf.1 8.1 (Berkeley) 6/6/93
32 .\" $FreeBSD: head/usr.bin/printf/printf.1 264743 2014-04-21 22:47:18Z pfg $
42 .Ar format Op Ar arguments ...
46 utility formats and prints its arguments, after the first, under control
51 is a character string which contains three types of objects: plain characters,
52 which are simply copied to standard output, character escape sequences which
53 are converted and copied to the standard output, and format specifications,
54 each of which causes printing of the next successive
59 after the first are treated as strings if the corresponding format is
64 otherwise it is evaluated as a C constant, with the following extensions:
66 .Bl -bullet -offset indent -compact
68 A leading plus or minus sign is allowed.
70 If the leading character is a single or double quote, the value is the
71 character code of the next character.
74 The format string is reused as often as necessary to satisfy the
76 Any extra format specifications are evaluated with zero or the null
79 Character escape sequences are in backslash notation as defined in the
82 The characters and their meanings
85 .Bl -tag -width Ds -offset indent -compact
87 Write a <bell> character.
89 Write a <backspace> character.
91 Ignore remaining characters in this string.
93 Write a <form-feed> character.
95 Write a <new-line> character.
97 Write a <carriage return> character.
99 Write a <tab> character.
101 Write a <vertical tab> character.
103 Write a <single quote> character.
105 Write a backslash character.
108 value is the 1-, 2-, or 3-digit
111 Multibyte characters can be constructed using multiple
116 Each format specification is introduced by the percent character
118 The remainder of the format specification includes,
119 in the following order:
121 .It "Zero or more of the following flags:"
125 specifying that the value should be printed in an ``alternate form''.
130 formats, this option has no effect.
133 formats the precision of the number is increased to force the first
134 character of the output string to a zero.
138 format, a non-zero result has the string
143 .Cm a , A , e , E , f , F , g
146 formats, the result will always contain a decimal point, even if no
147 digits follow the point (normally, a decimal point only appears in the
148 results of those formats if a digit follows the decimal point).
153 formats, trailing zeros are not removed from the result as they
156 A minus sign `\-' which specifies
158 of the output in the indicated field;
160 A `+' character specifying that there should always be
161 a sign placed before the number when using signed formats.
163 A space specifying that a blank should be left before a positive number
165 A `+' overrides a space if both are used;
167 A zero `0' character indicating that zero-padding should be used
168 rather than blank-padding.
169 A `\-' overrides a `0' if both are used;
172 An optional digit string specifying a
174 if the output string has fewer bytes than the field width it will
175 be blank-padded on the left (or right, if the left-adjustment indicator
176 has been given) to make up the field width (note that a leading zero
177 is a flag, but an embedded zero is part of a field width);
181 followed by an optional digit string giving a
183 which specifies the number of digits to appear after the decimal point,
188 formats, or the maximum number of bytes to be printed
189 from a string; if the digit string is missing, the precision is treated
192 A character which indicates the type of format to use (one of
193 .Cm diouxXfFeEgGaAcsb ) .
194 The uppercase formats differ from their lowercase counterparts only in
195 that the output of the former is entirely in uppercase.
196 The floating-point format specifiers
198 may be prefixed by an
200 to request that additional precision be used, if available.
203 A field width or precision may be
205 instead of a digit string.
208 supplies the field width or precision.
210 The format characters and their meanings are:
215 is printed as a signed decimal (d or i), unsigned octal, unsigned decimal,
216 or unsigned hexadecimal (X or x), respectively.
220 is printed in the style `[\-]ddd.ddd' where the number of d's
221 after the decimal point is equal to the precision specification for
223 If the precision is missing, 6 digits are given; if the precision
224 is explicitly 0, no digits and no decimal point are printed.
225 The values \*[If] and \*[Na] are printed as
233 is printed in the style
236 .Sq Op - Ar d.ddd No \(+- Ar dd
239 is one digit before the decimal point and the number after is equal to
240 the precision specification for the argument; when the precision is
241 missing, 6 digits are produced.
242 The values \*[If] and \*[Na] are printed as
256 whichever gives full precision in minimum space.
262 .Sq Op - Ar h.hhh No \(+- Li p Ar d
264 where there is one digit before the hexadecimal point and the number
265 after is equal to the precision specification for the argument;
266 when the precision is missing, enough digits are produced to convey
267 the argument's exact double-precision floating-point representation.
268 The values \*[If] and \*[Na] are printed as
278 Bytes from the string
280 are printed until the end is reached or until the number of bytes
281 indicated by the precision specification is reached; however if the
282 precision is 0 or missing, the string is printed entirely.
286 but interpret character escapes in backslash notation in the string
288 The permitted escape sequences are slightly different in that
294 Allows reordering of the output according to
297 Print a `%'; no argument is used.
301 character is defined in the program's locale (category
304 In no case does a non-existent or small field width cause truncation of
305 a field; padding takes place only if the specified field width exceeds
308 Some shells may provide a builtin
310 command which is similar or identical to this utility.
319 behavior of converting arguments of numeric formats not beginning
322 code of the first character is not supported.
331 command is expected to be compatible with the
340 after the standard library function,
344 hexadecimal character constants were deliberately not provided.
346 Trying to print a dash ("-") as the first character causes
348 to interpret the dash as a program argument.
353 If the locale contains multibyte characters
361 formats with a precision
362 may not operate as expected.
364 Since the floating point numbers are translated from
366 to floating-point and
367 then back again, floating-point precision may be lost.
368 (By default, the number is translated to an IEEE-754 double-precision
369 value before being printed.
372 modifier may produce additional precision, depending on the hardware platform.)
374 The escape sequence \e000 is the string terminator.
375 When present in the argument for the
377 format, the argument will be truncated at the \e000 character.
379 Multibyte characters are not recognized in format strings (this is only
382 can appear inside a multibyte character).