Switch to SpeakEasy.net DSL

The Modular Manual Browser

Home Page
Manual: (OSF1-V5.1-alpha)
Apropos / Subsearch:
optional field

checknr(1)							   checknr(1)


  checknr - Checks nroff files


  checknr [-fs]	[-a.x1.y1.x2.y2	... .xn.yn] [-c.x1.x2.x3 ... .xn] [file...]

  The checknr command checks a list of nroff input files for certain kinds of
  errors involving mismatched opening and closing delimiters and unknown com-


  -a.x1.y1.x2.y2 ... .xn.yn
      Adds pairs of macros to the list.	 This option 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
      -a.BS.ES.	 (You cannot use the -a	option to define a 1-character macro

  -c.x1.x2.x3 ... .xn
      Defines otherwise	undefined commands.

  -f  Causes checknr to	ignore \f font changes.

  -s  Causes checknr to	ignore \s size changes.


  If no	files are specified, checknr checks the	standard input.	 Delimiters
  checked are as follows:

    +  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 command can handle both the ms and me macro packages.

  The checknr command is intended to be	used on	documents that are prepared
  with checknr in mind,	much the same as lint. 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 go
  directly into	the next font or explicitly specify the	original font or
  point	size, and many existing	documents actually do this, such a practice
  produces error messages from checknr.

  The checknr command does not recognize certain reasonable constructs,	such
  as conditionals.


  Commands:  deroff(1),	neqn(1), nroff(1), tbl(1)