| blob | 836a00e85271713852e244778280442cfa36cbd1 |
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.
5 .\"
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
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.
21 .\"
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
32 .\" SUCH DAMAGE.
33 .\"
34 .\" @(#)indent.1 8.1 (Berkeley) 7/1/93
35 .\" $FreeBSD: src/usr.bin/indent/indent.1,v 1.27 2005/07/31 03:30:45 keramida Exp $
36 .\" $DragonFly: src/usr.bin/indent/indent.1,v 1.3 2006/03/26 22:56:57 swildner Exp $
37 .\"
38 .Dd April 6, 2009
39 .Dt INDENT 1
40 .Os
41 .Sh NAME
42 .Nm indent
43 .Nd indent and format C program source
44 .Sh SYNOPSIS
45 .Nm
46 .Op Ar input-file Op Ar output-file
47 .Op Fl bad | Fl nbad
48 .Op Fl bap | Fl nbap
49 .Bk -words
50 .Op Fl bbb | Fl nbbb
51 .Ek
52 .Op Fl \&bc | Fl nbc
53 .Op Fl \&bl
54 .Op Fl \&br
55 .Op Fl c Ns Ar n
56 .Op Fl \&cd Ns Ar n
57 .Bk -words
58 .Op Fl cdb | Fl ncdb
59 .Ek
60 .Op Fl \&ce | Fl nce
61 .Op Fl \&ci Ns Ar n
62 .Op Fl cli Ns Ar n
63 .Op Fl d Ns Ar n
64 .Op Fl \&di Ns Ar n
65 .Bk -words
66 .Op Fl fbs | Fl nfbs
67 .Op Fl fc1 | Fl nfc1
68 .Op Fl fcb | Fl nfcb
69 .Ek
70 .Op Fl i Ns Ar n
71 .Op Fl \&ip | Fl nip
72 .Op Fl l Ns Ar n
73 .Op Fl \&lc Ns Ar n
74 .Op Fl \&ldi Ns Ar n
75 .Op Fl \&lp | Fl nlp
76 .Op Fl npro
77 .Op Fl pcs | Fl npcs
78 .Op Fl psl | Fl npsl
79 .Op Fl \&sc | Fl nsc
80 .Bk -words
81 .Op Fl sob | Fl nsob
82 .Ek
83 .Op Fl \&st
84 .Op Fl troff
85 .Op Fl ut | Fl nut
86 .Op Fl v | Fl \&nv
87 .Sh DESCRIPTION
88 The
89 .Nm
90 utility is a
91 .Em C
92 program formatter.
93 It reformats the
94 .Em C
95 program in the
96 .Ar input-file
97 according to the switches.
98 The switches which can be specified are described below.
99 They may appear before or after the file names.
100 .Pp
101 .Sy NOTE :
102 If you only specify an
103 .Ar input-file ,
104 the formatting is
105 done `in-place', that is, the formatted file is written back into
106 .Ar input-file
107 and a backup copy of
108 .Ar input-file
109 is written in the current directory.
110 If
111 .Ar input-file
112 is named
113 .Sq Pa /blah/blah/file ,
114 the backup file is named
115 .Sq Pa file.BAK .
116 .Pp
117 If
118 .Ar output-file
119 is specified,
120 .Nm
121 checks to make sure that it is different from
122 .Ar input-file .
123 .Pp
124 The options listed below control the formatting style imposed by
125 .Nm .
126 .Bl -tag -width Op
127 .It Fl bad , nbad
128 If
129 .Fl bad
130 is specified, a blank line is forced after every block of
131 declarations.
132 Default:
133 .Fl nbad .
134 .It Fl bap , nbap
135 If
136 .Fl bap
137 is specified, a blank line is forced after every procedure body.
138 Default:
139 .Fl nbap .
140 .It Fl bbb , nbbb
141 If
142 .Fl bbb
143 is specified, a blank line is forced before every block comment.
144 Default:
145 .Fl nbbb .
146 .It Fl \&bc , nbc
147 If
148 .Fl \&bc
149 is specified, then a newline is forced after each comma in a declaration.
150 .Fl nbc
151 turns off this option.
152 Default:
153 .Fl \&nbc .
154 .It Fl \&br , \&bl
155 Specifying
156 .Fl \&bl
157 lines-up compound statements like this:
158 .Bd -literal -offset indent
159 if (...)
160 {
161 code
162 }
163 .Ed
164 .Pp
165 Specifying
166 .Fl \&br
167 (the default) makes them look like this:
168 .Bd -literal -offset indent
169 if (...) {
170 code
171 }
172 .Ed
173 .Pp
174 .It Fl c Ns Ar n
175 The column in which comments on code start.
176 The default is 33.
177 .It Fl cd Ns Ar n
178 The column in which comments on declarations start.
179 The default is for these comments to start in the same column as those on code.
180 .It Fl cdb , ncdb
181 Enables (disables) the placement of comment delimiters on blank lines.
182 With this option enabled, comments look like this:
183 .Bd -literal -offset indent
184 /*
185 * this is a comment
186 */
187 .Ed
188 .Pp
189 Rather than like this:
190 .Bd -literal -offset indent
191 /* this is a comment */
192 .Ed
193 .Pp
194 This only affects block comments, not comments to the right of code.
195 The default is
196 .Fl cdb .
197 .It Fl ce , nce
198 Enables (disables) forcing of `else's to cuddle up to the immediately preceding
199 `}'.
200 The default is
201 .Fl \&ce .
202 .It Fl \&ci Ns Ar n
203 Sets the continuation indent to be
204 .Ar n .
205 Continuation
206 lines will be indented that far from the beginning of the first line of the
207 statement.
208 Parenthesized expressions have extra indentation added to
209 indicate the nesting, unless
210 .Fl \&lp
211 is in effect or the continuation indent is exactly half of the main indent.
212 .Fl \&ci
213 defaults to the same value as
214 .Fl i .
215 .It Fl cli Ns Ar n
216 Causes case labels to be indented
217 .Ar n
218 tab stops to the right of the containing
219 .Ic switch
220 statement.
221 .Fl cli0.5
222 causes case labels to be indented half a tab stop.
223 The default is
224 .Fl cli0 .
225 .It Fl d Ns Ar n
226 Controls the placement of comments which are not to the right of code.
227 For example,
228 .Fl \&d\&1
229 means that such comments are placed one indentation level to the left of code.
230 Specifying the default
231 .Fl \&d\&0
232 lines-up these comments with the code.
233 See the section on comment indentation below.
234 .It Fl \&di Ns Ar n
235 Specifies the indentation, in character positions,
236 of global variable names and all struct/union member names
237 relative to the beginning of their type declaration.
238 The default is
239 .Fl di16 .
240 .It Fl dj , ndj
241 .Fl \&dj
242 left justifies declarations.
243 .Fl ndj
244 indents declarations the same as code.
245 The default is
246 .Fl ndj .
247 .It Fl \&ei , nei
248 Enables (disables) special
249 .Ic else-if
250 processing.
251 If it is enabled, an
252 .Ic if
253 following an
254 .Ic else
255 will have the same indentation as the preceding
256 .Ic \&if
257 statement.
258 The default is
259 .Fl ei .
260 .It Fl fbs , nfbs
261 Enables (disables) splitting the function declaration and opening brace
262 across two lines.
263 The default is
264 .Fl fbs .
265 .It Fl fc1 , nfc1
266 Enables (disables) the formatting of comments that start in column 1.
267 Often, comments whose leading `/' is in column 1 have been carefully
268 hand formatted by the programmer.
269 In such cases,
270 .Fl nfc1
271 should be used.
272 The default is
273 .Fl fc1 .
274 .It Fl fcb , nfcb
275 Enables (disables) the formatting of block comments (ones that begin
276 with `/*\\n').
277 Often, block comments have been not so carefully hand formatted by the
278 programmer, but reformatting that would just change the line breaks is not
279 wanted.
280 In such cases,
281 .Fl nfcb
282 should be used.
283 Block comments are then handled like box comments.
284 The default is
285 .Fl fcb .
286 .It Fl i Ns Ar n
287 The number of spaces for one indentation level.
288 The default is 8.
289 .It Fl \&ip , nip
290 Enables (disables) the indentation of parameter declarations from the left
291 margin.
292 The default is
293 .Fl \&ip .
294 .It Fl l Ns Ar n
295 Maximum length of an output line.
296 The default is 78.
297 .It Fl \&ldi Ns Ar n
298 Specifies the indentation, in character positions,
299 of local variable names
300 relative to the beginning of their type declaration.
301 The default is for local variable names to be indented
302 by the same amount as global ones.
303 .It Fl \&lp , nlp
304 Lines-up code surrounded by parenthesis in continuation lines.
305 If a line
306 has a left paren which is not closed on that line, then continuation lines
307 will be lined up to start at the character position just after the left
308 paren.
309 For example, here is how a piece of continued code looks with
310 .Fl nlp
311 in effect:
312 .Bd -literal -offset indent
313 p1 = first_procedure(second_procedure(p2, p3),
314 \ \ third_procedure(p4, p5));
315 .Ed
316 .Pp
317 With
318 .Fl lp
319 in effect (the default) the code looks somewhat clearer:
320 .Bd -literal -offset indent
321 p1\ =\ first_procedure(second_procedure(p2,\ p3),
322 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4,\ p5));
323 .Ed
324 .Pp
325 Inserting two more newlines we get:
326 .Bd -literal -offset indent
327 p1\ =\ first_procedure(second_procedure(p2,
328 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ p3),
329 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4,
330 \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ p5));
331 .Ed
332 .It Fl npro
333 Causes the profile files,
334 .Sq Pa ./.indent.pro
335 and
336 .Sq Pa ~/.indent.pro ,
337 to be ignored.
338 .It Fl pcs , npcs
339 If true
340 .Pq Fl pcs
341 all procedure calls will have a space inserted between the name and the `('.
342 The default is
343 .Fl npcs .
344 .It Fl psl , npsl
345 If true
346 .Pq Fl psl
347 the names of procedures being defined are placed in
348 column 1 \- their types, if any, will be left on the previous lines.
349 The default is
350 .Fl psl .
351 .It Fl \&sc , nsc
352 Enables (disables) the placement of asterisks (`*'s) at the left edge of all
353 comments.
354 The default is
355 .Fl sc .
356 .It Fl sob , nsob
357 If
358 .Fl sob
359 is specified, indent will swallow optional blank lines.
360 You can use this to get rid of blank lines after declarations.
361 Default:
362 .Fl nsob .
363 .It Fl \&st
364 Causes
365 .Nm
366 to take its input from stdin and put its output to stdout.
367 .It Fl T Ns Ar typename
368 Adds
369 .Ar typename
370 to the list of type keywords.
371 Names accumulate:
372 .Fl T
373 can be specified more than once.
374 You need to specify all the typenames that
375 appear in your program that are defined by
376 .Ic typedef
377 \- nothing will be
378 harmed if you miss a few, but the program will not be formatted as nicely as
379 it should.
380 This sounds like a painful thing to have to do, but it is really
381 a symptom of a problem in C:
382 .Ic typedef
383 causes a syntactic change in the
384 language and
385 .Nm
386 cannot find all
387 instances of
388 .Ic typedef .
389 .It Fl troff
390 Causes
391 .Nm
392 to format the program for processing by
393 .Xr troff 1 .
394 It will produce a fancy
395 listing in much the same spirit as
396 .Xr vgrind 1 .
397 If the output file is not specified, the default is standard output,
398 rather than formatting in place.
399 .It Fl ut , nut
400 Enables (disables) the use of tab characters in the output.
401 Tabs are assumed to be aligned on columns divisible by 8.
402 The default is
403 .Fl ut .
404 .It Fl v , \&nv
405 .Fl v
406 turns on `verbose' mode;
407 .Fl \&nv
408 turns it off.
409 When in verbose mode,
410 .Nm
411 reports when it splits one line of input into two or more lines of output,
412 and gives some size statistics at completion.
413 The default is
414 .Fl \&nv .
415 .El
416 .Pp
417 You may set up your own `profile' of defaults to
418 .Nm
419 by creating a file called
420 .Pa .indent.pro
421 in your login directory and/or the current directory and including
422 whatever switches you like.
423 A `.indent.pro' in the current directory takes
424 precedence over the one in your login directory.
425 If
426 .Nm
427 is run and a profile file exists, then it is read to set up the program's
428 defaults.
429 Switches on the command line, though, always override profile switches.
430 The switches should be separated by spaces, tabs or newlines.
431 .Ss Comments
432 .Sq Em Box
433 .Em comments .
434 The
435 .Nm
436 utility
437 assumes that any comment with a dash or star immediately after the start of
438 comment (that is, `/*\-' or `/**') is a comment surrounded by a box of stars.
439 Each line of such a comment is left unchanged, except that its indentation
440 may be adjusted to account for the change in indentation of the first line
441 of the comment.
442 .Pp
443 .Em Straight text .
444 All other comments are treated as straight text.
445 The
446 .Nm
447 utility fits as many words (separated by blanks, tabs, or newlines) on a
448 line as possible.
449 Blank lines break paragraphs.
450 .Ss Comment indentation
451 If a comment is on a line with code it is started in the `comment column',
452 which is set by the
453 .Fl c Ns Ns Ar n
454 command line parameter.
455 Otherwise, the comment is started at
456 .Ar n
457 indentation levels less than where code is currently being placed, where
458 .Ar n
459 is specified by the
460 .Fl d Ns Ns Ar n
461 command line parameter.
462 If the code on a line extends past the comment
463 column, the comment starts further to the right, and the right margin may be
464 automatically extended in extreme cases.
465 .Ss Preprocessor lines
466 In general,
467 .Nm
468 leaves preprocessor lines alone.
469 The only reformatting that it will do is to straighten up trailing comments.
470 It leaves embedded comments alone.
471 Conditional compilation
472 .Pq Ic #ifdef...#endif
473 is recognized and
474 .Nm
475 attempts to correctly
476 compensate for the syntactic peculiarities introduced.
477 .Ss C syntax
478 The
479 .Nm
480 utility understands a substantial amount about the syntax of C, but it
481 has a `forgiving' parser.
482 It attempts to cope with the usual sorts of incomplete and misformed syntax.
483 In particular, the use of macros like:
484 .Pp
485 .Dl #define forever for(;;)
486 .Pp
487 is handled properly.
488 .Sh ENVIRONMENT
489 The
490 .Nm
491 utility uses the
492 .Ev HOME
493 environment variable.
494 .Sh FILES
495 .Bl -tag -width "./.indent.pro" -compact
496 .It Pa ./.indent.pro
497 profile file
498 .It Pa ~/.indent.pro
499 profile file
500 .El
501 .Sh HISTORY
502 The
503 .Nm
504 command appeared in
505 .Bx 4.2 .
506 .Sh BUGS
507 The
508 .Nm
509 utility has even more switches than
510 .Xr ls 1 .
511 .Pp
512 A common mistake is to try to indent all the
513 .Em C
514 programs in a directory by typing:
515 .Pp
516 .Dl indent *.c
517 .Pp
518 This is probably a bug, not a feature.