1 .\" $NetBSD: indent.1,v 1.18 2005/09/11 23:17:34 wiz Exp $
3 .\" Copyright (c) 1980, 1990, 1993
4 .\" The Regents of the University of California. 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. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" Copyright (c) 1985 Sun Microsystems, Inc.
31 .\" Copyright (c) 1976 Board of Trustees of the University of Illinois.
32 .\" All rights reserved.
34 .\" Redistribution and use in source and binary forms, with or without
35 .\" modification, are permitted provided that the following conditions
37 .\" 1. Redistributions of source code must retain the above copyright
38 .\" notice, this list of conditions and the following disclaimer.
39 .\" 2. Redistributions in binary form must reproduce the above copyright
40 .\" notice, this list of conditions and the following disclaimer in the
41 .\" documentation and/or other materials provided with the distribution.
42 .\" 3. All advertising materials mentioning features or use of this software
43 .\" must display the following acknowledgement:
44 .\" This product includes software developed by the University of
45 .\" California, Berkeley and its contributors.
46 .\" 4. Neither the name of the University nor the names of its contributors
47 .\" may be used to endorse or promote products derived from this software
48 .\" without specific prior written permission.
50 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
51 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
52 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
53 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
54 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
55 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
56 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
57 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
58 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
59 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
62 .\" from: @(#)indent.1 8.1 (Berkeley) 7/1/93
69 .Nd indent and format C program source
73 .Op Ar input-file Op Ar output-file
76 .Op Fl bacc | Fl nbacc
143 according to the switches.
144 The switches which can be specified are described below.
145 They may appear before or after the file names.
148 If you only specify an
151 done `in-place', that is, the formatted file is written back into
155 is written in the current directory.
159 .Sq Pa /blah/blah/file ,
160 the backup file is named
167 checks to make sure it is different from
170 The options listed below control the formatting style imposed by
176 is specified, a blank line is forced around every conditional
178 For example, in front of every #ifdef and after every #endif.
179 Other blank lines surrounding such blocks will be swallowed.
185 is specified, a blank line is forced after every block of
192 is specified, a blank line is forced after every procedure body.
198 is specified, a blank line is forced before every block comment.
204 is specified, then a newline is forced after each comma in a declaration.
206 turns off this option.
212 lines up compound statements like this:
213 .Bd -literal -offset indent
222 (the default) makes them look like this:
223 .Bd -literal -offset indent
232 is specified, a blank is forced after
237 The column in which comments on code start.
241 The column in which comments on declarations start.
243 is for these comments to start in the same column as those on code.
245 Enables (disables) the placement of comment delimiters on blank lines.
246 With this option enabled, comments look like this:
247 .Bd -literal -offset indent
253 Rather than like this:
254 .Bd -literal -offset indent
255 /* this is a comment */
258 This only affects block comments, not comments to the right of
263 Enables (disables) forcing `else's to cuddle up to the immediately preceding
268 Sets the continuation indent to be
271 lines will be indented that far from the beginning of the first line of the
273 Parenthesized expressions have extra indentation added to
274 indicate the nesting, unless
278 defaults to the same value as
281 Causes case labels to be indented
283 tab stops to the right of the containing
287 causes case labels to be indented half a tab stop.
291 Controls the placement of comments which are not to the right of code.
294 means that such comments are placed one indentation level to the left of code.
295 Specifying the default
297 lines up these comments with the code.
298 See the section on comment
301 Specifies the indentation, in character positions, from a declaration keyword
302 to the following identifier.
307 left justifies declarations.
309 indents declarations the same as code.
313 Enables (disables) special
320 will have the same indentation as the preceding
326 Enables (disables) extra indentation on continuation lines of
327 the expression part of
332 These continuation lines will be indented one extra level.
336 Enables (disables) the formatting of comments that start in column 1.
337 Often, comments whose leading `/' is in column 1 have been carefully
338 hand formatted by the programmer.
345 The number of spaces for one indentation level.
349 Enables (disables) the indentation of parameter declarations from the left
354 Maximum length of an output line.
358 Lines up code surrounded by parenthesis in continuation lines.
359 If a line has a left paren which is not closed on that line, then
360 continuation lines will be lined up to start at the character
361 position just after the left paren.
362 For example, here is how a piece of continued code looks with
365 .Bd -literal -offset indent
366 p1 = first_procedure(second_procedure(p2, p3),
367 \ \ third_procedure(p4,p5));
372 in effect (the default) the code looks somewhat clearer:
373 .Bd -literal -offset indent
374 p1\ =\ first_procedure(second_procedure(p2,\ p3),
375 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4,p5));
378 Inserting two more newlines we get:
379 .Bd -literal -offset indent
380 p1\ =\ first_procedure(second_procedure(p2,
381 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ p3),
382 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4
383 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ p5));
386 Causes the profile files,
389 .Sq Pa ~/.indent.pro ,
394 all procedure calls will have a space inserted between
395 the name and the `('.
401 the names of procedures being defined are placed in
402 column 1 \- their types, if any, will be left on the previous lines.
406 Enables (disables) the placement of asterisks (`*'s) at the left edge of all
413 is specified, indent will swallow optional blank lines.
414 You can use this to get rid of blank lines after declarations.
420 to take its input from stdin, and put its output to stdout.
421 .It Fl T Ns Ar typename
424 to the list of type keywords.
427 can be specified more than once.
428 You need to specify all the typenames that
429 appear in your program that are defined by
432 harmed if you miss a few, but the program won't be formatted as nicely as
434 This sounds like a painful thing to have to do, but it's really
435 a symptom of a problem in C:
437 causes a syntactic change in the
446 to format the program for processing by
448 It will produce a fancy
449 listing in much the same spirit as
451 If the output file is not specified, the default is standard output,
452 rather than formatting in place.
455 turns on `verbose' mode;
458 When in verbose mode,
460 reports when it splits one line of input into two or more lines of output,
461 and gives some size statistics at completion.
466 You may set up your own `profile' of defaults to
468 by creating a file called
470 in your login directory and/or the current directory and including
471 whatever switches you like.
472 A `.indent.pro' in the current directory takes
473 precedence over the one in your login directory.
476 is run and a profile file exists, then it is read to set up the program's
478 Switches on the command line, though, always override profile switches.
479 The switches should be separated by spaces, tabs or newlines.
484 assumes that any comment with a dash or star immediately after the start of
485 comment (that is, `/*\-' or `/**') is a comment surrounded by a box of stars.
486 Each line of such a comment is left unchanged, except that its indentation
487 may be adjusted to account for the change in indentation of the first line
491 All other comments are treated as straight text.
493 fits as many words (separated by blanks, tabs, or newlines) on a
495 Blank lines break paragraphs.
496 .Ss Comment indentation
497 If a comment is on a line with code it is started in the `comment column',
500 command line parameter.
501 Otherwise, the comment is started at
503 indentation levels less than where code is currently being placed, where
507 command line parameter.
508 If the code on a line extends past the comment
509 column, the comment starts further to the right, and the right margin may be
510 automatically extended in extreme cases.
511 .Ss Preprocessor lines
514 leaves preprocessor lines alone.
515 The only reformatting that it will do is to straighten up trailing comments.
516 It leaves embedded comments alone.
517 Conditional compilation
518 .Pq Ic #ifdef...#endif
521 attempts to correctly
522 compensate for the syntactic peculiarities introduced.
525 understands a substantial amount about the syntax of C, but it
526 has a `forgiving' parser.
527 It attempts to cope with the usual sorts of incomplete and misformed syntax.
528 In particular, the use of macros like:
530 .Dl #define forever for(;;)
537 environment variable.
539 .Bl -tag -width "./.indent.pro" -compact
552 has even more switches than
555 A common mistake that often causes grief is typing:
559 to the shell in an attempt to indent all the
561 programs in a directory.
562 This is probably a bug, not a feature.