version 1.95, 2010/05/07 15:49:36 |
version 1.99, 2010/05/12 08:41:17 |
|
|
.Sq \e*(Ba |
.Sq \e*(Ba |
.Pq vertical bar . |
.Pq vertical bar . |
.Ss Whitespace |
.Ss Whitespace |
In non-literal free-form lines, consecutive blocks of whitespace are |
Whitespace consists of the space character. |
pruned from input and added later in the output filter, if applicable: |
In free-form lines, whitespace is preserved within a line; un-escaped |
.Bd -literal -offset indent |
trailing spaces are stripped from input (unless in a literal context). |
These spaces are pruned from input. |
Blank free-form lines, which may include whitespace, are only permitted |
\&.Bd \-literal |
within literal contexts. |
These are not. |
|
\&.Ed |
|
.Ed |
|
.Pp |
.Pp |
In macro lines, whitespace delimits arguments and is discarded. If |
In macro lines, whitespace delimits arguments and is discarded. If |
arguments are quoted, whitespace within the quotes is retained. |
arguments are quoted, whitespace within the quotes is retained. |
.Pp |
|
Blank lines are only permitted within literal contexts, as are lines |
|
containing only whitespace. Tab characters are only acceptable when |
|
delimiting |
|
.Sq \&Bl \-column |
|
or when in a literal context. |
|
.Ss Quotation |
.Ss Quotation |
Macro arguments may be quoted with a double-quote to group |
Macro arguments may be quoted with a double-quote to group |
space-delimited terms or to retain blocks of whitespace. A quoted |
space-delimited terms or to retain blocks of whitespace. A quoted |
|
|
\&.Nm |
\&.Nm |
utility processes files ... |
utility processes files ... |
\&.\e\*q .Sh IMPLEMENTATION NOTES |
\&.\e\*q .Sh IMPLEMENTATION NOTES |
\&.\e\*q The next is for sections 1 & 8 only. |
|
\&.\e\*q .Sh EXIT STATUS |
|
\&.\e\*q The next is for sections 2, 3, & 9 only. |
\&.\e\*q The next is for sections 2, 3, & 9 only. |
\&.\e\*q .Sh RETURN VALUES |
\&.\e\*q .Sh RETURN VALUES |
\&.\e\*q The next is for sections 1, 6, 7, & 8 only. |
\&.\e\*q The next is for sections 1, 6, 7, & 8 only. |
\&.\e\*q .Sh ENVIRONMENT |
\&.\e\*q .Sh ENVIRONMENT |
\&.\e\*q .Sh FILES |
\&.\e\*q .Sh FILES |
|
\&.\e\*q The next is for sections 1 & 8 only. |
|
\&.\e\*q .Sh EXIT STATUS |
\&.\e\*q .Sh EXAMPLES |
\&.\e\*q .Sh EXAMPLES |
\&.\e\*q The next is for sections 1, 4, 6, 7, & 8 only. |
\&.\e\*q The next is for sections 1, 4, 6, 7, & 8 only. |
\&.\e\*q .Sh DIAGNOSTICS |
\&.\e\*q .Sh DIAGNOSTICS |
Line 461 Manuals not documenting a command won't include the ab |
|
Line 452 Manuals not documenting a command won't include the ab |
|
Implementation-specific notes should be kept here. This is useful when |
Implementation-specific notes should be kept here. This is useful when |
implementing standard functions that may have side effects or notable |
implementing standard functions that may have side effects or notable |
algorithmic implications. |
algorithmic implications. |
.It Em EXIT STATUS |
|
Command exit status for section 1, 6, and 8 manuals. This section is |
|
the dual of |
|
.Em RETURN VALUES , |
|
which is used for functions. Historically, this information was |
|
described in |
|
.Em DIAGNOSTICS , |
|
a practise that is now discouraged. |
|
.Pp |
|
See |
|
.Sx \&Ex . |
|
.It Em RETURN VALUES |
.It Em RETURN VALUES |
This section is the dual of |
This section is the dual of |
.Em EXIT STATUS , |
.Em EXIT STATUS , |
Line 492 short description of how the file is used (created, mo |
|
Line 472 short description of how the file is used (created, mo |
|
.Pp |
.Pp |
See |
See |
.Sx \&Pa . |
.Sx \&Pa . |
|
.It Em EXIT STATUS |
|
Command exit status for section 1, 6, and 8 manuals. This section is |
|
the dual of |
|
.Em RETURN VALUES , |
|
which is used for functions. Historically, this information was |
|
described in |
|
.Em DIAGNOSTICS , |
|
a practise that is now discouraged. |
|
.Pp |
|
See |
|
.Sx \&Ex . |
.It Em EXAMPLES |
.It Em EXAMPLES |
Example usages. This often contains snippets of well-formed, |
Example usages. This often contains snippets of well-formed, |
well-tested invocations. Make doubly sure that your examples work |
well-tested invocations. Make doubly sure that your examples work |