checknr(1)checknr(1)Namechecknr - check nroff/troff files
Syntaxchecknr [-s] [-f] [-a.x1.y1.x2.y2. ... .xn.yn] [-c.x1.x2.x3... .xn]
The command checks a list of or input files for certain kinds of errors
involving mismatched opening and closing delimiters and unknown com‐
mands. If no files are specified, checks the standard input. Delim‐
iters checked are:
5 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 command knows about the and macro packages.
The command is intended to be used on documents that are prepared with
in mind, much the same as 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 Since it is probably better to
use the \fP and \s0 forms anyway, you should think of this as a contri‐
bution to your document preparation style.
Options-a Allows additional pairs of macros to be added to the list. 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 exam‐
ple, to define a pair .BS and .ES, use -a.BS.ES.
-c Defines commands otherwise complained about as undefined.
-f Ignores \f font changes.
-s Ignores \s size changes.
There is no way to define a 1 character macro name using -a.
Does not correctly recognize certain reasonable characters, such as
Complaints about unmatched delimiters.
Complaints about unrecognized commands.
Various complaints about the syntax of commands.
See Alsoeqn(1), nroff(1), troff(1), ms(7), me(7)checknr(1)