.\" Copyright (c) 1980 Regents of the University of California.
.\" All rights reserved. The Berkeley software License Agreement
.\" specifies the terms and conditions for redistribution.
.\" @(#)checknr.1 6.2 (Berkeley) 5/7/86
.TH CHECKNR 1 "May 7, 1986"
checknr \- check nroff/troff files
.BR \-a ".x1.y1.x2.y2. ... .xn.yn"
.BR \-c ".x1.x2.x3 ... .xn"
input files for certain kinds of errors
involving mismatched opening and closing delimiters
If no files are specified,
checks the standard input.
Font changes using \efx ... \efP.
Size changes using \esx ... \es0.
Macros that come in open ... close forms, for example,
the .TS and .TE macros which must always come in pairs.
Additional pairs of macros can be added to the list using the
This must be followed by groups of six characters, each group defining
and the second macro name.
For example, to define a pair .BS and .ES, use \-\fBa\fP.BS.ES
option defines commands which would otherwise be complained about
to ignore \ef font changes.
to ignore \es size changes.
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 \ef and \es commands,
in that each \efx must be terminated with \efP and
each \esx must be terminated with \es0.
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 \efP and \es0 forms anyway,
you should think of this as a contribution to your document
nroff(1), troff(1), checkeq(1), ms(7), me(7)
Complaints about unmatched delimiters.
Complaints about unrecognized commands.
Various complaints about the syntax of commands.
There is no way to define a 1 character macro name using
Does not correctly recognize certain reasonable constructs,