mandoc/mandoc.1 - diff

Return to mandoc.1 CVS log

Up to [cvsweb.bsd.lv] / mandoc

Diff for /mandoc/mandoc.1 between version 1.201 and 1.230

version 1.201, 2017/06/17 23:07:00

version 1.230, 2018/10/02 14:56:47

Line 1

.\" $Id$

.\"

.\" Permission to use, copy, modify, and distribute this software for any

.\" purpose with or without fee is hereby granted, provided that the above

Line 34

.Sh DESCRIPTION

The

.Nm

utility formats

utility formats manual pages for display.

.Ux

manual pages for display.

.Pp

By default,

.Nm

Line 75 and for the

Line 73 and for the

.Xr man 7

.Ic \&TH

macro.

This can also be used to perform style checks according to the

conventions of one operating system while running on a different

operating system; see

.Sx Style messages

for details.

.It Fl K Ar encoding

Specify the input encoding.

The supported

Line 123 With

Line 116 With

all input files are interpreted as

.Xr man 7 .

By default, the input language is automatically detected for each file:

if the the first macro is

if the first macro is

.Ic \&Dd

.Ic \&Dt ,

Line 137 With other arguments,

Line 130 With other arguments,

is silently ignored.

.It Fl O Ar options

Comma-separated output options.

See the descriptions of the individual output formats for supported

.Ar options .

.It Fl T Ar output

Output format.

Select the output format.

See

Supported values for the

.Sx Output Formats

.Ar output

for available formats.

argument are

Defaults to

.Cm ascii ,

.Fl T Cm locale .

.Cm html ,

the default of

.Cm locale ,

.Cm man ,

.Cm markdown ,

.Cm pdf ,

.Cm ps ,

.Cm tree ,

and

.Cm utf8 .

.Pp

The special

.Fl T Cm lint

mode only parses the input and produces no output.

It implies

.Fl W Cm all

and redirects parser messages, which usually appear on standard

error output, to standard output.

.It Fl W Ar level

Specify the minimum message

.Ar level

Line 151 to be reported on the standard error output and to aff

Line 163 to be reported on the standard error output and to aff

The

.Ar level

can be

.Cm base ,

.Cm style ,

.Cm warning ,

.Cm error ,

.Cm unsupp ;

.Cm unsupp .

The

.Cm base

level automatically derives the operating system from the contents of the

.Ic \&Os

macro, from the

.Fl Ios

command line option, or from the

.Xr uname 3

return value.

The levels

.Cm openbsd

and

.Cm netbsd

are variants of

.Cm base

that bypass autodetection and request validation of base system

conventions for a particular operating system.

The level

.Cm all

is an alias for

.Cm style .

.Cm base .

By default,

.Nm

is silent.

Line 182 and

Line 213 and

are requested, they can be joined with a comma, for example

.Fl W Cm error , Ns Cm stop .

.It Ar file

Read input from zero or more files.

Read from the given input file.

If unspecified, reads from stdin.

If multiple files are specified, they are processed in the given order.

If multiple files are specified,

If unspecified,

.Nm

will halt with the first failed parse.

reads from standard input.

.El

.Pp

The options

Line 206 manual.

Line 237 manual.

The options

.Fl fkl

are mutually exclusive and override each other.

.Ss Output Formats

The

.Nm

utility accepts the following

.Fl T

arguments, which correspond to output modes:

.Bl -tag -width "-T markdown"

.It Fl T Cm ascii

Produce 7-bit ASCII output.

See

.Sx ASCII Output .

.It Fl T Cm html

Produce HTML5, CSS1, and MathML output.

See

.Sx HTML Output .

.It Fl T Cm lint

Parse only: produce no output.

Implies

.Fl W Cm style .

.It Fl T Cm locale

Encode output using the current locale.

This is the default.

See

.Sx Locale Output .

.It Fl T Cm man

Produce

.Xr man 7

format output.

See

.Sx Man Output .

.It Fl T Cm markdown

Produce output in

.Sy markdown

format.

See

.Sx Markdown Output .

.It Fl T Cm pdf

Produce PDF output.

See

.Sx PDF Output .

.It Fl T Cm ps

Produce PostScript output.

See

.Sx PostScript Output .

.It Fl T Cm tree

Produce an indented parse tree.

See

.Sx Syntax tree output .

.It Fl T Cm utf8

Encode output in the UTF\-8 multi-byte format.

See

.Sx UTF\-8 Output .

.El

.Pp

If multiple input files are specified, these will be processed by the

corresponding filter in-order.

.Ss ASCII Output

Output produced by

Use

.Fl T Cm ascii

is rendered in standard 7-bit ASCII documented in

to force text output in 7-bit ASCII character encoding documented in the

.Xr ascii 7 .

.Xr ascii 7

manual page, ignoring the

.Xr locale 1

set in the environment.

.Pp

Font styles are applied by using back-spaced encoding such that an

underlined character

Line 283 The special characters documented in

Line 261 The special characters documented in

.Xr mandoc_char 7

are rendered best-effort in an ASCII equivalent.

.Pp

Output width is limited to 78 visible columns unless literal input lines

exceed this limit.

.Pp

The following

.Fl O

arguments are accepted:

Line 299 and seven for

Line 274 and seven for

.Xr man 7 .

Increasing this is not recommended; it may result in degraded formatting,

for example overfull lines or ugly line breaks.

When output is to a pager on a terminal that is less than 66 columns

wide, the default is reduced to three columns.

.It Cm mdoc

Format

.Xr man 7

input files in

.Xr mdoc 7

output style.

Specifically, this suppresses the two additional blank lines near the

top and the bottom of each page, and it implies

.Fl O Cm indent Ns =5 .

One useful application is for checking that

.Fl T Cm man

output formats in the same way as the

.Xr mdoc 7

source it was generated from.

.It Cm width Ns = Ns Ar width

The output width is set to

.Ar width .

.Ar width

instead of the default of 78.

When output is to a pager on a terminal that is less than 79 columns

wide, the default is reduced to one less than the terminal width.

In any case, lines that are output in literal mode are never wrapped

and may exceed the output width.

.El

.Ss HTML Output

Output produced by

Line 322 defaults to simple output (via an embedded style-sheet

Line 318 defaults to simple output (via an embedded style-sheet

readable in any graphical or text-based web

browser.

.Pp

Special characters are rendered in decimal-encoded UTF\-8.

Non-ASCII characters are rendered

as hexadecimal Unicode character references.

.Pp

The following

.Fl O

Line 348 Instances of

Line 345 Instances of

are replaced with the include filename.

The default is not to present a

hyperlink.

.It Cm man Ns = Ns Ar fmt

.It Cm man Ns = Ns Ar fmt Ns Op ; Ns Ar fmt

The string

.Ar fmt ,

for example,

Line 364 are replaced with the linked manual's name and section

Line 361 are replaced with the linked manual's name and section

If no section is included, section 1 is assumed.

The default is not to

present a hyperlink.

If two formats are given and a file

.Ar %N.%S

exists in the current directory, the first format is used;

otherwise, the second format is used.

.It Cm style Ns = Ns Ar style.css

The file

.Ar style.css

is used for an external style-sheet.

This must be a valid absolute or

relative URI.

.It Cm toc

If an input file contains at least two non-standard sections,

print a table of contents near the beginning of the output.

.El

.Ss Locale Output

Locale-depending output encoding is triggered with

By default,

.Nm

automatically selects UTF-8 or ASCII output according to the current

.Xr locale 1 .

If any of the environment variables

.Ev LC_ALL ,

.Ev LC_CTYPE ,

.Ev LANG

are set and the first one that is set

selects the UTF-8 character encoding, it produces

.Sx UTF-8 Output ;

otherwise, it falls back to

.Sx ASCII Output .

This output mode can also be selected explicitly with

.Fl T Cm locale .

This is the default.

.Pp

This option is not available on all systems: systems without locale

support, or those whose internal representation is not natively UCS-4,

will fall back to

.Fl T Cm ascii .

See

.Sx ASCII Output

for font style specification and available command-line arguments.

.Ss Man Output

Translate input format into

Use

.Fl T Cm man

to translate

.Xr mdoc 7

input into

.Xr man 7

output format.

This is useful for distributing manual sources to legacy systems

Line 392 lacking

Line 405 lacking

.Xr mdoc 7

formatters.

.Pp

If the input format of a file is

.Xr mdoc 7

is passed as input, it is translated into

.Xr man 7 .

If the input format is

.Xr man 7 ,

the input is copied to the output, expanding any

.Xr roff 7

Line 408 level controls which

Line 417 level controls which

.Sx DIAGNOSTICS

are displayed before copying the input to the output.

.Ss Markdown Output

Translate

Use

.Fl T Cm markdown

to translate

.Xr mdoc 7

input to the

input to the markdown format conforming to

.Sy markdown

format conforming to

.Lk http://daringfireball.net/projects/markdown/syntax.text\

"John Gruber's 2004 specification" .

The output also almost conforms to the

Line 483 If an unknown value is encountered,

Line 492 If an unknown value is encountered,

.Ar letter

is used.

.El

.Ss UTF\-8 Output

.Ss UTF-8 Output

Use

.Fl T Cm utf8

to force a UTF\-8 locale.

to force text output in UTF-8 multi-byte character encoding,

ignoring the

.Xr locale 1

settings in the environment.

See

.Sx Locale Output

.Sx ASCII Output

for details and options.

regarding font styles and

.Fl O

arguments.

.Pp

On operating systems lacking locale or wide character support, and

on those where the internal character representation is not UCS-4,

.Nm

always falls back to

.Sx ASCII Output .

.Ss Syntax tree output

Use

.Fl T Cm tree

Line 558 Meta data is not available in this case.

Line 578 Meta data is not available in this case.

.El

.Sh ENVIRONMENT

.Bl -tag -width MANPAGER

.It Ev LC_CTYPE

The character encoding

.Xr locale 1 .

When

.Sx Locale Output

is selected, it decides whether to use ASCII or UTF-8 output format.

It never affects the interpretation of input files.

.It Ev MANPAGER

Any non-empty value of the environment variable

.Ev MANPAGER

Line 596 option:

Line 623 option:

.Pp

.Bl -tag -width Ds -compact

.It 0

No style suggestions, warnings or errors occurred, or those that

No base system convention violations, style suggestions, warnings,

did were ignored because they were lower than the requested

or errors occurred, or those that did were ignored because they

were lower than the requested

.Ar level .

.It 1

At least one style suggestion occurred, but no warning or error, and

At least one base system convention violation or style suggestion

occurred, but no warning or error, and

.Fl W Cm base

.Fl W Cm style

was specified.

.It 2

At least one warning occurred, but no error, and

.Fl W Cm warning

or a lower

.Fl W Cm style

.Ar level

was specified.

was requested.

.It 3

At least one parsing error occurred,

but no unsupported feature was encountered, and

Line 636 to exit at once, possibly in the middle of parsing or

Line 667 to exit at once, possibly in the middle of parsing or

Note that selecting

.Fl T Cm lint

output mode implies

.Fl W Cm style .

.Fl W Cm all .

.Sh EXAMPLES

To page manuals to the terminal:

.Pp

Line 669 parser:

Line 700 parser:

Messages displayed by

.Nm

follow this format:

.Bd -ragged -offset indent

.Nm :

.Ar file : Ns Ar line : Ns Ar column : level : message : macro args

.Pq Ar os

.Ed

.Pp

.D1 Nm Ns : Ar file : Ns Ar line : Ns Ar column : level : message : macro args

.Pp

Line and column numbers start at 1.

Both are omitted for messages referring to an input file as a whole.

Macro names and arguments are omitted where meaningless.

The

.Ar os

operating system specifier is omitted for messages that are relevant

for all operating systems.

Fatal messages about invalid command line arguments

or operating system errors, for example when memory is exhausted,

may also omit the

Line 694 so using GNU troff instead of

Line 732 so using GNU troff instead of

.Nm

to process the file may be preferable.

.It Cm error

An input file contains invalid syntax that cannot be safely interpreted.

Indicates a risk of information loss or severe misformatting,

By discarding part of the input or inserting missing tokens,

in most cases caused by serious syntax errors.

the parser is able to continue, and the error does not prevent

generation of formatted output, but typically, preparing that

output involves information loss, broken document structure

or unintended formatting, no matter whether

.Nm

or GNU troff is used.

In many cases, the output of

.Nm

and GNU troff is identical, but in some,

.Nm

is more resilient than GNU troff with respect to malformed input.

.Pp

Non-existent or unreadable input files are also reported on the

.Cm error

level.

In that case, the parser cannot even be started and no output

is produced from those input files.

.It Cm warning

An input file uses obsolete, discouraged or non-portable syntax.

Indicates a risk that the information shown or its formatting

All the same, the meaning of the input is unambiguous and a correct

may mismatch the author's intent in minor ways.

rendering can be produced.

Additionally, syntax errors are classified at least as warnings,

Documents causing warnings may render poorly when using other

even if they do not usually cause misformatting.

formatting tools instead of

.Nm .

.It Cm style

An input file uses dubious or discouraged style.

This is not a complaint about the syntax, and probably neither

Line 732 so it may occasionally issue bogus suggestions.

Line 751 so it may occasionally issue bogus suggestions.

Please use your good judgement to decide whether any particular

.Cm style

suggestion really justifies a change to the input file.

.It Cm base

A convention used in the base system of a specific operating system

is not adhered to.

These are not markup mistakes, and neither the quality of formatting

nor portability are in danger.

Messages of the

.Cm base

level are printed with the more intuitive

.Cm style

.Ar level

tag.

.El

.Pp

Messages of the

.Cm base ,

.Cm style ,

.Cm warning ,

.Cm error ,

Line 746 are hidden unless their level, or a lower level, is re

Line 777 are hidden unless their level, or a lower level, is re

option or

.Fl T Cm lint

output mode.

.Ss Style messages

.Pp

As indicated below, some style checks are only performed if a

As indicated below, all

specific operating system name occurs in the arguments of the

.Cm base

and some

.Cm style

checks are only performed if a specific operating system name occurs

in the arguments of the

.Fl W

command line option, of the

.Ic \&Os

macro, of the

.Fl Ios

Line 756 command line option, or, if neither are present, in th

Line 793 command line option, or, if neither are present, in th

of the

.Xr uname 3

function.

.Ss Conventions for base system manuals

.Bl -ohang

.It Sy "Mdocdate found"

.Pq mdoc , Nx

Line 778 macro does not use CVS

Line 816 macro does not use CVS

keyword substitution, but using it is conventionally expected in the

.Ox

base system.

.It Sy "unknown architecture"

.Pq mdoc , Ox , Nx

The third argument of the

.Ic \&Dt

macro does not match any of the architectures this operating system

is running on.

.It Sy "operating system explicitly specified"

.Pq mdoc , Ox , Nx

The

.Ic \&Os

macro has an argument.

In the base system, it is conventionally left blank.

.It Sy "RCS id missing"

.Pq Ox , Nx

The manual page lacks the comment line with the RCS identifier

generated by CVS

.Ic OpenBSD

.Ic NetBSD

keyword substitution as conventionally used in these operating systems.

.It Sy "referenced manual not found"

.Pq mdoc

.Ic \&Xr

macro references a manual page that is not found in the base system.

The path to look for base system manuals is configurable at compile

time and defaults to

.Pa /usr/share/man : /usr/X11R6/man .

.El

.Ss Style suggestions

.Bl -ohang

.It Sy "legacy man(7) date format"

.Pq mdoc

The

Line 791 Consider using the conventional

Line 860 Consider using the conventional

date format

.Dq "Month dd, yyyy"

instead.

.It Sy "RCS id missing"

.It Sy "normalizing date format to" : No ...

.Pq Ox , Nx

.Pq mdoc , man

The manual page lacks the comment line with the RCS identifier

The

generated by CVS

.Ic \&Dd

.Ic OpenBSD

.Ic NetBSD

.Ic \&TH

keyword substitution as conventionally used in these operating systems.

macro provides an abbreviated month name or a day number with a

leading zero.

In the formatted output, the month name is written out in full

and the leading zero is omitted.

.It Sy "lower case character in document title"

.Pq mdoc , man

The title is still used as given in the

.Ic \&Dt

.Ic \&TH

macro.

.It Sy "duplicate RCS id"

A single manual page contains two copies of the RCS identifier for

the same operating system.

Consider deleting the later instance and moving the first one up

to the top of the page.

.It Sy "possible typo in section name"

.Pq mdoc

Fuzzy string matching revealed that the argument of an

.Ic \&Sh

macro is similar, but not identical to a standard section name.

.It Sy "unterminated quoted argument"

.Pq roff

Macro arguments can be enclosed in double quote characters

such that space characters and macro names contained in the quoted

argument need not be escaped.

The closing quote of the last argument of a macro can be omitted.

However, omitting it is not recommended because it makes the code

harder to read.

.It Sy "useless macro"

.Pq mdoc

Line 839 list contains two consecutive

Line 930 list contains two consecutive

entries describing the same

.Ic \&Er

number.

.It Sy "description line ends with a full stop"

.It Sy "trailing delimiter"

.Pq mdoc

Do not use punctuation at the end of an

The last argument of an

.Ic \&Nd

.Ic \&Ex , \&Fo , \&Nd , \&Nm , \&Os , \&Sh , \&Ss , \&St ,

block.

.Ic \&Sx

macro ends with a trailing delimiter.

This is usually bad style and often indicates typos.

Most likely, the delimiter can be removed.

.It Sy "no blank before trailing delimiter"

.Pq mdoc

The last argument of a macro that supports trailing delimiter

arguments is longer than one byte and ends with a trailing delimiter.

Consider inserting a blank such that the delimiter becomes a separate

argument, thus moving it out of the scope of the macro.

.It Sy "fill mode already enabled, skipping"

.Pq man

.Ic \&fi

request occurs even though the document is still in fill mode,

or already switched back to fill mode.

It has no effect.

.It Sy "fill mode already disabled, skipping"

.Pq man

.Ic \&nf

request occurs even though the document already switched to no-fill mode

and did not switch back to fill mode yet.

It has no effect.

.It Sy "verbatim \(dq--\(dq, maybe consider using \e(em"

.Pq mdoc

Even though the ASCII output device renders an em-dash as

.Qq \-\- ,

that is not a good way to write it in an input file

because it renders poorly on all other output devices.

.It Sy "function name without markup"

.Pq mdoc

A word followed by an empty pair of parentheses occurs on a text line.

Line 858 Consider using an

Line 973 Consider using an

.Ic \&Xr

macro.

.It Sy "whitespace at end of input line"

.Pq mdoc , man , roff

Whitespace at the end of input lines is almost never semantically

significant \(em but in the odd case where it might be, it is

extremely confusing when reviewing and maintaining documents.

.It Sy "bad comment style"

.Pq roff

Comment lines start with a dot, a backslash, and a double-quote character.

The

.Nm

utility treats the line as a comment line even without the backslash,

but leaving out the backslash might not be portable.

.El

.Ss Warnings related to the document prologue

.Bl -ohang

Line 873 macro before the first non-prologue macro.

Line 1000 macro before the first non-prologue macro.

There is no

.Ic \&TH

macro, or it has no arguments.

.It Sy "lower case character in document title"

.Pq mdoc , man

The title is still used as given in the

.Ic \&Dt

.Ic \&TH

macro.

.It Sy "missing manual section, using \(dq\(dq"

.Pq mdoc , man

Line 915 The date given in a

Line 1035 The date given in a

.Ic \&TH

macro does not follow the conventional format.

.It Sy "date in the future, using it anyway"

.Pq mdoc , man

The date given in a

.Ic \&Dd

.Ic \&TH

macro is more than a day ahead of the current system

.Xr time 3 .

.It Sy "missing Os macro, using \(dq\(dq"

.Pq mdoc

The default or current system is not shown in this case.

.It Sy "duplicate prologue macro"

.Pq mdoc

One of the prologue macros occurs more than once.

The last instance overrides all previous ones.

.It Sy "late prologue macro"

.Pq mdoc

Line 929 A

Line 1053 A

.Ic \&Os

macro occurs after some non-prologue macro, but still takes effect.

.It Sy "skipping late title macro"

.Pq mdoc

The

.Ic \&Dt

macro appears after the first non-prologue macro.

Traditional formatters cannot handle this because

they write the page header before parsing the document body.

Even though this technical restriction does not apply to

.Nm ,

traditional semantics is preserved.

The late macro is discarded including its arguments.

.It Sy "prologue macros out of order"

.Pq mdoc

The prologue macros are not given in the conventional order

Line 1031 The same standard section title occurs more than once.

Line 1144 The same standard section title occurs more than once.

.Pq mdoc

A standard section header occurs in a section of the manual

where it normally isn't useful.

.It Sy "cross reference to self"

.Pq mdoc

.Ic \&Xr

macro refers to a name and section matching the section of the present

manual page and a name mentioned in an

.Ic \&Nm

macro in the NAME or SYNOPSIS section, or in an

.Ic \&Fn

.Ic \&Fo

macro in the SYNOPSIS.

Consider using

.Ic \&Nm

.Ic \&Fn

instead of

.Ic \&Xr .

.It Sy "unusual Xr order"

.Pq mdoc

In the SEE ALSO section, an

Line 1117 The paragraph macro is moved after the end of the list

Line 1248 The paragraph macro is moved after the end of the list

.Pq mdoc

An input line begins with an

.Ic \&Ns

macro.

macro, or the next argument after an

.Ic \&Ns

macro is an isolated closing delimiter.

The macro is ignored.

.It Sy "blocks badly nested"

.Pq mdoc

Line 1158 list block contains text or macros before the first

Line 1291 list block contains text or macros before the first

.Ic \&It

macro.

The offending children are moved before the beginning of the list.

.It Sy "fill mode already enabled, skipping"

.It Sy "first macro on line"

.Pq man

Inside a

.Ic \&Bl Fl column

.Ic \&fi

list, a

request occurs even though the document is still in fill mode,

.Ic \&Ta

or already switched back to fill mode.

macro occurs as the first macro on a line, which is not portable.

It has no effect.

.It Sy "fill mode already disabled, skipping"

.Pq man

.Ic \&nf

request occurs even though the document already switched to no-fill mode

and did not switch back to fill mode yet.

It has no effect.

.It Sy "line scope broken"

.Pq man

While parsing the next-line scope of the previous macro,

Line 1225 A

Line 1350 A

.Ic \&Bl ,

.Ic \&D1 ,

.Ic \&Dl ,

.Ic \&MT ,

.Ic \&RS ,

.Ic \&UR

Line 1302 list, an

Line 1428 list, an

.Ic \&It

block is empty.

An empty list item is shown.

.It Sy "missing argument, using next line"

.Pq mdoc

.Ic \&It

macro in a

.Ic \&Bd Fl column

list has no arguments.

While

.Nm

uses the text or macros of the following line, if any, for the cell,

other formatters may misformat the list.

.It Sy "missing font type, using \efR"

.Pq mdoc

Line 1360 An empty pair of square brackets is shown.

Line 1497 An empty pair of square brackets is shown.

.It Sy "missing resource identifier, using \(dq\(dq"

.Pq man

The

.Ic \&MT

.Ic \&UR

macro is invoked without any argument.

An empty pair of angle brackets is shown.

Line 1371 An empty box is inserted.

Line 1510 An empty box is inserted.

.El

.Ss "Warnings related to bad macro arguments"

.Bl -ohang

.It Sy "unterminated quoted argument"

.Pq roff

Macro arguments can be enclosed in double quote characters

such that space characters and macro names contained in the quoted

argument need not be escaped.

The closing quote of the last argument of a macro can be omitted.

However, omitting it is not recommended because it makes the code

harder to read.

.It Sy "duplicate argument"

.Pq mdoc

Line 1482 or

Line 1613 or

.Cm off .

The invalid argument is moved out of the macro, which leaves the macro

empty, causing it to toggle the spacing mode.

.It Sy "argument contains two font escapes"

.Pq roff

The second argument of a

.Ic char

request contains more than one font escape sequence.

A wrong font may remain active after using the character.

.It Sy "unknown font, skipping request"

.Pq man , tbl

Line 1520 As an implementation dependent choice, tab characters

Line 1657 As an implementation dependent choice, tab characters

are passed through to the formatters in any case.

Given that the text before the tab character will be filled,

it is hard to predict which tab stop position the tab will advance to.

.It Sy "whitespace at end of input line"

.Pq mdoc , man , roff

Whitespace at the end of input lines is almost never semantically

significant \(em but in the odd case where it might be, it is

extremely confusing when reviewing and maintaining documents.

.It Sy "new sentence, new line"

.Pq mdoc

A new sentence starts in the middle of a text line.

Start it on a new input line to help formatters produce correct spacing.

.It Sy "bad comment style"

.Pq roff

Comment lines start with a dot, a backslash, and a double-quote character.

The

.Nm

utility treats the line as a comment line even without the backslash,

but leaving out the backslash might not be portable.

.It Sy "invalid escape sequence"

.Pq roff

An escape sequence has an invalid opening argument delimiter, lacks the

Line 1642 and any remaining cells stay empty.

Line 1767 and any remaining cells stay empty.

.El

.Ss "Errors related to roff, mdoc, and man code"

.Bl -ohang

.It Sy "duplicate prologue macro"

.Pq mdoc

One of the prologue macros occurs more than once.

The last instance overrides all previous ones.

.It Sy "skipping late title macro"

.Pq mdoc

The

.Ic \&Dt

macro appears after the first non-prologue macro.

Traditional formatters cannot handle this because

they write the page header before parsing the document body.

Even though this technical restriction does not apply to

.Nm ,

traditional semantics is preserved.

The late macro is discarded including its arguments.

.It Sy "input stack limit exceeded, infinite loop?"

.Pq roff

Explicit recursion limits are implemented for the following features,

Line 1680 or

Line 1820 or

macro.

It may be mistyped or unsupported.

The request or macro is discarded including its arguments.

.It Sy "skipping request outside macro"

.Pq roff

.Ic shift

.Ic return

request occurs outside any macro definition and has no effect.

.It Sy "skipping insecure request"

.Pq roff

An input file attempted to run a shell command

Line 1712 An

Line 1859 An

.Xr mdoc 7

block closing macro, a

.Xr man 7

.Ic \&RE

.Ic \&ME , \&RE

.Ic \&UE

macro, an

Line 1746 At the end of the document, an explicit

Line 1893 At the end of the document, an explicit

block, a

.Xr man 7

next-line scope or

.Ic \&RS

.Ic \&MT , \&RS

.Ic \&UR

block, an equation, table, or

Line 1789 When parsing for a request or a user-defined macro nam

Line 1936 When parsing for a request or a user-defined macro nam

only the escape sequence is discarded.

The characters preceding it are used as the request or macro name,

the characters following it are used as the arguments to the request or macro.

.It Sy "using macro argument outside macro"

.Pq roff

The escape sequence \e$ occurs outside any macro definition

and expands to the empty string.

.It Sy "argument number is not numeric"

.Pq roff

The argument of the escape sequence \e$ is not a digit;

the escape sequence expands to the empty string.

.It Sy "NOT IMPLEMENTED: Bd -file"

.Pq mdoc

For security reasons, the

Line 1817 macro fails to specify the list type.

Line 1972 macro fails to specify the list type.

The argument of a

.Ic \&ce

request is not a number.

.It Sy "argument is not a character"

.Pq roff

The first argument of a

.Ic char

request is neither a single ASCII character

nor a single character escape sequence.

The request is ignored including all its arguments.

.It Sy "missing manual name, using \(dq\(dq"

.Pq mdoc

The first call to

Line 1851 or

Line 2013 or

.Ic \&gsize

statement has a non-numeric or negative argument or no argument at all.

The invalid request or statement is ignored.

.It Sy "excessive shift"

.Pq roff

The argument of a

.Ic shift

request is larger than the number of arguments of the macro that is

currently being executed.

All macro arguments are deleted and \en(.$ is set to zero.

.It Sy "NOT IMPLEMENTED: .so with absolute path or \(dq..\(dq"

.Pq roff

For security reasons,

Line 1918 A macro or request is invoked with too many arguments:

Line 2087 A macro or request is invoked with too many arguments:

.Bl -dash -offset 2n -width 2n -compact

.It

.Ic \&Fo ,

.Ic \&MT ,

.Ic \&PD ,

.Ic \&RS ,

.Ic \&UR ,

CVSweb