|CHECKNR(1)||FreeBSD General Commands Manual||CHECKNR(1)|
NAMEchecknr — check nroff/troff files
|checknr||[ -a.x1.y1.x2.y2. ... .xn.yn][ -c.x1.x2.x3 ... .xn][ -s][ -f] file|
DESCRIPTIONThe checknr utility checks a list of nroff(1) or troff(1) input files for certain kinds of errors involving mismatched opening and closing delimiters and unknown commands. If no files are specified, checknr checks the standard input.
The following options are available:
Add additional pairs of macros to the list of known macros. This must be followed by groups of six characters, each group defining a pair of macros. The six characters are a period, the first macro name, another period, and the second macro name. For example, to define a pair .BS and .ES, use ‘
- Define commands which would otherwise be complained about as undefined.
checknr to ignore ‘
\f’ font changes.
\s’ size changes.
Delimiters checked are:
- Font changes using \fx ... \fP.
- Size changes using \sx ... \s0.
- Macros that come in open ... close forms, for example, the .TS and .TE macros which must always come in pairs.
The checknr utility is intended for use on documents that are prepared with checknr in mind, much the same as lint(1). It expects a certain document writing style for ‘
\f’ and ‘
\s’ commands, in that each ‘
\fx’ must be terminated with ‘
\fP’ and each ‘
\sx’ must be terminated with ‘
\s0’. While it will work to directly go into the next font or explicitly specify the original font or point size, and many existing documents actually do this, such a practice will produce complaints from checknr. Since it is probably better to use the ‘
\fP’ and ‘
\s0’ forms anyway, you should think of this as a contribution to your document preparation style.
HISTORYThe checknr command appeared in 4.0BSD.
BUGSThere is no way to define a 1 character macro name using -a.
Does not correctly recognize certain reasonable constructs, such as conditionals.
Input lines are limited to LINE_MAX (2048) bytes in length.
|January 26, 2005||FreeBSD|