1 .\" Copyright (c) 1980, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
3 .\" Copyright (c) 1976 Board of Trustees of the University of Illinois.
4 .\" All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. All advertising materials mentioning features or use of this software
15 .\" must display the following acknowledgement:
16 .\" This product includes software developed by the University of
17 .\" California, Berkeley and its contributors.
18 .\" 4. Neither the name of the University nor the names of its contributors
19 .\" may be used to endorse or promote products derived from this software
20 .\" without specific prior written permission.
22 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
34 .\" @(#)indent.1 8.1 (Berkeley) 7/1/93
41 .Nd indent and format C program source
44 .Op Ar input-file Op Ar output-file
85 program formatter. It reformats the
89 according to the switches. The switches which can be
90 specified are described below. They may appear before or after the file
94 If you only specify an
97 done `in-place', that is, the formatted file is written back into
101 is written in the current directory. If
104 .Sq Pa /blah/blah/file ,
105 the backup file is named
112 checks to make sure it is different from
115 The options listed below control the formatting style imposed by
121 is specified, a blank line is forced after every block of
122 declarations. Default:
127 is specified, a blank line is forced after every procedure body. Default:
132 is specified, a blank line is forced before every block comment. Default:
137 is specified, then a newline is forced after each comma in a declaration.
139 turns off this option. Default:
144 lines-up compound statements like this:
146 .Bd -literal -offset indent
155 (the default) makes them look like this:
157 .Bd -literal -offset indent
164 The column in which comments on code start. The default is 33.
166 The column in which comments on declarations start. The default
167 is for these comments to start in the same column as those on code.
169 Enables (disables) the placement of comment delimiters on blank lines. With
170 this option enabled, comments look like this:
171 .Bd -literal -offset indent
178 Rather than like this:
179 .Bd -literal -offset indent
180 /* this is a comment */
183 This only affects block comments, not comments to the right of
187 Enables (disables) forcing of `else's to cuddle up to the immediately preceding
191 Sets the continuation indent to be
194 lines will be indented that far from the beginning of the first line of the
195 statement. Parenthesized expressions have extra indentation added to
196 indicate the nesting, unless
200 defaults to the same value as
203 Causes case labels to be indented
205 tab stops to the right of the containing
209 causes case labels to be indented half a tab stop. The
213 Controls the placement of comments which are not to the
214 right of code. For example,
216 means that such comments are placed one indentation level to the
217 left of code. Specifying the default
219 lines-up these comments with the code. See the section on comment
222 Specifies the indentation, in character positions, from a declaration keyword
223 to the following identifier. The default is
227 left justifies declarations.
229 indents declarations the same as code. The default is
232 Enables (disables) special
234 processing. If it's enabled, an
238 will have the same indentation as the preceding
240 statement. The default is
243 Enables (disables) the formatting of comments that start in column 1.
244 Often, comments whose leading `/' is in column 1 have been carefully
245 hand formatted by the programmer. In such cases,
251 The number of spaces for one indentation level. The default is 8.
253 Enables (disables) the indentation of parameter declarations from the left
254 margin. The default is
257 Maximum length of an output line. The default is 78.
259 Lines-up code surrounded by parenthesis in continuation lines. If a line
260 has a left paren which is not closed on that line, then continuation lines
261 will be lined up to start at the character position just after the left
262 paren. For example, here is how a piece of continued code looks with
266 .Bd -literal -offset indent
267 p1 = first_procedure(second_procedure(p2, p3),
268 \ \ third_procedure(p4, p5));
274 in effect (the default) the code looks somewhat clearer:
275 .Bd -literal -offset indent
276 p1\ =\ first_procedure(second_procedure(p2,\ p3),
277 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4,\ p5));
281 Inserting two more newlines we get:
282 .Bd -literal -offset indent
283 p1\ =\ first_procedure(second_procedure(p2,
284 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ p3),
285 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4,
286 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ p5));
289 Causes the profile files,
292 .Sq Pa ~/.indent.pro ,
297 all procedure calls will have a space inserted between
298 the name and the `('. The default is
303 the names of procedures being defined are placed in
304 column 1 \- their types, if any, will be left on the previous lines. The
308 Enables (disables) the placement of asterisks (`*'s) at the left edge of all
309 comments. The default is
314 is specified, indent will swallow optional blank lines. You can use this to
315 get rid of blank lines after declarations. Default:
320 to take its input from stdin and put its output to stdout.
321 .It Fl T Ns Ar typename
324 to the list of type keywords. Names accumulate:
326 can be specified more than once. You need to specify all the typenames that
327 appear in your program that are defined by
330 harmed if you miss a few, but the program won't be formatted as nicely as
331 it should. This sounds like a painful thing to have to do, but it's really
332 a symptom of a problem in C:
334 causes a syntactic change in the
343 to format the program for processing by
345 It will produce a fancy
346 listing in much the same spirit as
348 If the output file is not specified, the default is standard output,
349 rather than formatting in place.
352 turns on `verbose' mode;
354 turns it off. When in verbose mode,
356 reports when it splits one line of input into two or more lines of output,
357 and gives some size statistics at completion. The default is
361 You may set up your own `profile' of defaults to
363 by creating a file called
365 in your login directory and/or the current directory and including
366 whatever switches you like. A `.indent.pro' in the current directory takes
367 precedence over the one in your login directory. If
369 is run and a profile file exists, then it is read to set up the program's
370 defaults. Switches on the command line, though, always override profile
371 switches. The switches should be separated by spaces, tabs or newlines.
377 assumes that any comment with a dash or star immediately after the start of
378 comment (that is, `/*\-' or `/**') is a comment surrounded by a box of stars.
379 Each line of such a comment is left unchanged, except that its indentation
380 may be adjusted to account for the change in indentation of the first line
384 All other comments are treated as straight text.
386 fits as many words (separated by blanks, tabs, or newlines) on a
387 line as possible. Blank lines break paragraphs.
389 .Ss Comment indentation
390 If a comment is on a line with code it is started in the `comment column',
393 command line parameter. Otherwise, the comment is started at
395 indentation levels less than where code is currently being placed, where
399 command line parameter. If the code on a line extends past the comment
400 column, the comment starts further to the right, and the right margin may be
401 automatically extended in extreme cases.
403 .Ss Preprocessor lines
406 leaves preprocessor lines alone. The only
407 reformatting that it will do is to straighten up trailing comments. It
408 leaves embedded comments alone. Conditional compilation
409 .Pq Ic #ifdef...#endif
412 attempts to correctly
413 compensate for the syntactic peculiarities introduced.
417 understands a substantial amount about the syntax of C, but it
418 has a `forgiving' parser. It attempts to cope with the usual sorts of
419 incomplete and misformed syntax. In particular, the use of macros like:
421 .Dl #define forever for(;;)
428 environment variable.
430 .Bl -tag -width "./.indent.pro" -compact
443 has even more switches than
447 A common mistake that often causes grief is typing:
451 to the shell in an attempt to indent all the
453 programs in a directory.
454 This is probably a bug, not a feature.