+Rather than like this:
+.nf
+.ft L
+ /* this is a comment */
+.ft R
+.fi
+This only affects block comments, not comments to the right of code. The default is
+.B \-cdb .
+.TP 15
+.BI \-ce , \-nce
+Enables (disables) forcing `else's to cuddle up to the immediatly preceeding
+`}'. The default is
+.B \-ce .
+.TP 15
+.BI \-ci n
+Sets the continuation indent to be \fIn\fR. Continuation
+lines will be indented that far from the beginning of the first line of the
+statement. Parenthesized expressions have extra indentation added to
+indicate the nesting, unless \fB\-lp\fR is in effect.
+\fB\-ci\fR defaults to the same value as \fB\-i\fR.
+.TP 15
+.BI \-cli n
+Causes case labels to be indented
+.I n
+tab stops to the right of the containing \fBswitch\fR statement.
+\fB-cli0.5\fR causes case labels to be indented half a tab stop. The
+default is
+.B \-cli0 .
+.TP 15
+.BI \-d n
+Controls the placement of comments which are not to the
+right of code. The default
+.B \-d1
+means that such comments are placed one indentation level to the
+left of code. Specifying
+.B \-d0
+lines up these comments with the code. See the section on comment
+indentation below.
+.TP 15
+.BI \-di n
+Specifies the indentation, in character positions, from a declaration keyword
+to the following identifier. The default is
+.B \-di16 .
+.if 0 \{.TP 15
+.BR \-dj , \-ndj
+.B \-dj
+left justifies declarations.
+.B \-ndj
+indents declarations the same as code. The default is
+.BR \-ndj .
+.TP 15
+.BI \-ei , \-nei
+Enables (disables) special
+.B else-if
+processing. If it's enabled,
+.BR if "s"
+following
+.BR else "s"
+will have the same indendation as the preceeding
+.B if
+statement.\}
+.TP 15
+.BI \-fc1 , \-nfc1
+Enables (disables) the formatting of comments that start in column 1.
+Often, comments whose leading `/' is in column 1 have been carefully
+hand formatted by the programmer. In such cases, \fB\-nfc1\fR should be
+used. The default is \fB\-fc1\fR.
+.TP 15
+.BI \-i n
+The number of spaces for one indentation level. The default is 4.
+.TP 15
+.BI \-ip , \-nip
+Enables (disables) the indentation of parameter declarations from the left
+margin. The default is
+.B \-ip .
+.TP 15
+.BI \-l n
+Maximum length of an output line. The default is 75.
+.TP 15
+.B \-npro
+Causes the profile files, `./.indent.pro' and `~/.indent.pro', to be ignored.
+.TP 15
+.BI \-lp , \-nlp
+Lines up code surrounded by parenthesis in continuation lines. If a line
+has a left paren which is not closed on that line, then continuation lines
+will be lined up to start at the character position just after the left
+paren. For example, here is how a piece of continued code looks with -nlp
+in effect:
+.ne 2
+.nf
+.ft L
+ p1 = first_procedure(second_procedure(p2, p3),
+ third_procedure(p4, p5));
+.ft R
+.fi
+.ne 5
+With \fB-lp\fR in effect (the default) the code looks somewhat clearer:
+.nf
+.ft L
+ p1 = first_procedure(second_procedure(p2, p3),
+ third_procedure(p4, p5));
+.ft R
+.fi
+.ne 5
+Inserting a couple more newlines we get:
+.nf
+.ft L
+ p1 = first_procedure(second_procedure(p2,
+ p3),
+ third_procedure(p4,
+ p5));
+.ft R
+.fi
+.TP 15
+.B \-pcs , \-npcs
+If true (\fB-pcs\fR) all procedure calls will have a space inserted between
+the name and the '('. The default is
+.B \-npcs
+.TP 15
+.B \-psl , \-npsl
+If true (\fB-psl\fR) the names of procedures being defined are placed in
+column 1 \- their types, if any, will be left on the previous lines. The
+default is
+.B -psl
+.TP 15
+.BI \-sc , \-nsc
+Enables (disables) the placement of asterisks (`*'s) at the left edge of all
+comments.
+.TP 15
+.BR \-sob , \-nsob
+If
+.B \-sob
+is specified, indent will swallow optional blank lines. You can use this to
+get rid of blank lines after declarations. Default:
+.B \-nsob
+.TP 15
+.B \-st
+Causes
+.B indent
+to take its input from stdin, and put its output to stdout.
+.TP 15
+.BI \-T typename
+Adds
+.I typename
+to the list of type keywords. Names accumulate:
+.B \-T
+can be specified more than once. You need to specify all the typenames that
+appear in your program that are defined by \fBtypedef\fRs \- nothing will be
+harmed if you miss a few, but the program won't be formatted as nicely as
+it should. This sounds like a painful thing to have to do, but it's really
+a symptom of a problem in C: \fBtypedef\fR causes a syntactic change in the
+laguage and \fIindent\fR can't find all \fBtypedef\fRs.
+.TP 15
+.B \-troff
+Causes
+.B indent
+to format the program for processing by troff. It will produce a fancy
+listing in much the same spirit as
+.BR vgrind.
+If the output file is not specified, the default is standard output,
+rather than formatting in place.
+.TP 15
+.BR \-v , \-nv
+.B \-v
+turns on `verbose' mode,
+.B \-nv
+turns it off. When in verbose mode,
+.I indent
+reports when it splits one line of input into two or more lines of output,
+and gives some size statistics at completion. The default is
+.BR \-nv .
+.SH "FURTHER DESCRIPTION"
+.LP
+You may set up your own `profile' of defaults to
+.I indent
+by creating a file called
+.BI . indent . pro
+in either your login directory or the current directory and including
+whatever switches you like. A `.indent.pro' in the current directory takes
+precedence over the one in your login directory. If
+.I indent
+is run and a profile file exists, then it is read to set up the program's
+defaults. Switches on the command line, though, always override profile
+switches. The switches should be separated by spaces, tabs or newlines.
+.LP
projects / unix-history / blobdiff