1 .\" $Id: man.7,v 1.4 2009/03/26 16:23:22 kristaps Exp $
3 .\" Copyright (c) 2009 Kristaps Dzonsons <kristaps@openbsd.org>
5 .\" Permission to use, copy, modify, and distribute this software for any
6 .\" purpose with or without fee is hereby granted, provided that the
7 .\" above copyright notice and this permission notice appear in all
10 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
11 .\" WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
12 .\" WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
13 .\" AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
14 .\" DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
15 .\" PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
16 .\" TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
17 .\" PERFORMANCE OF THIS SOFTWARE.
19 .Dd $Mdocdate: March 26 2009 $
25 .Nd man language reference
30 language was historically used to format
32 manuals. In this reference document, we describe the syntax and
40 to write your manuals. Use the
47 document follows simple rules: lines beginning with the control
50 are parsed for macros. Other lines are interpreted within the scope of
52 .Bd -literal -offset indent
53 \&.SH Macro lines change control state.
54 Other lines are interpreted within the current state.
58 Macros are character sequences whose structural rules are described
59 later in this document.
63 documents may contain only graphable 7-bit ASCII characters and the
70 Blank lines are acceptable; where found, the output will also assert a
75 escape is common in historical
77 documents; if encountered at the end of a word, it ensures that the
78 subsequent word isn't off-set by whitespace.
80 .Ss Special Characters
81 Special character sequences begin with the escape character
83 followed by either an open-parenthesis
85 for two-character sequences; an open-bracket
87 for n-character sequences (terminated at a close-bracket
89 or a single one-character sequence.
91 Characters may alternatively be escaped by a slash-asterisk,
93 with the same combinations as described above. This form is deprecated.
97 contains a table of all available escapes.
100 Macros are one to three three characters in length and begin with a
103 at the beginning of the line. An arbitrary amount of whitespace may
104 sit between the control character and the macro name. Thus,
112 macros follow the same structural rules:
113 .Bd -literal -offset indent
114 \&.YO \(lBbody...\(rB
119 consists of zero or more arguments to the macro.
122 has a primitive notion of multi-line scope for the following macros:
136 When these macros are invoked without arguments, the subsequent line is
137 considered a continuation of the macro. Thus:
138 .Bd -literal -offset indent
143 .Bd -literal -offset indent
148 are equivalent. If two consecutive lines exhibit the latter behaviour,
149 an error is raised. Thus, the following is acceptable:
150 .Bd -literal -offset indent
156 The following, however, is not:
157 .Bd -literal -offset indent
165 macro has similar behaviour, but does not need an empty argument line in
166 order to trigger scope.
169 This section contains a complete list of all
171 macros, arranged alphabetically, with the number of arguments.
173 .Bl -column "MacroX" "Arguments" -compact -offset indent
174 .It Em Macro Ta Em Arguments
203 utility was written by
204 .An Kristaps Dzonsons Aq kristaps@openbsd.org .
207 Do not use this language. Use