1 .\" Copyright (c) 1991, 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 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" @(#)wc.1 8.2 (Berkeley) 4/19/94
43 .Nd word, line, character, and byte count
51 utility displays the number of lines, words, and bytes contained in each
54 or standard input (if no file is specified) to the standard output.
55 A line is defined as a string of characters delimited by a
58 Characters beyond the final
60 character will not be included
63 A word is defined as a string of characters delimited by white space
65 White space characters are the set of characters for which the
67 function returns true.
68 If more than one input file is specified, a line of cumulative counts
69 for all the files is displayed on a separate line after the output for
72 The following options are available:
73 .Bl -tag -width indent
75 The number of bytes in each input file
76 is written to the standard output.
77 This will cancel out any prior usage of the
81 The number of lines in each input file
82 is written to the standard output.
84 The number of characters in each input file is written to the standard output.
85 If the current locale does not support multibyte characters, this
89 This will cancel out any prior usage of the
93 The number of words in each input file
94 is written to the standard output.
97 When an option is specified,
99 only reports the information requested by that option.
100 The order of output always takes the form of line, word,
102 The default action is equivalent to specifying the
108 If no files are specified, the standard input is used and no
109 file name is displayed.
110 The prompt will accept input until receiving EOF, or
112 in most environments.
118 environment variables affect the execution of
125 Count the number of characters, words and lines in each of the files
129 as well as the totals for both:
131 .Dl "wc -mlw report1 report2"
135 utility was documented to define a word as a
138 characters delimited by <space>, <tab> or <newline> characters
140 The implementation, however, did not handle non-printing characters
142 .Dq Li "\ \ ^D^E\ \ "
143 counted as 6 spaces, while
145 counted as 8 characters.
149 modified the implementation to be consistent
150 with the documentation.
151 This implementation defines a
155 function, as required by