1 .\" $Id: man.7,v 1.9 2009/04/12 19:19:57 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: April 12 2009 $
25 .Nd man language reference
30 language was historically used to format
32 manuals. This reference document describes the syntax and structure of
38 to write your manuals. Use the
45 document follows simple rules: lines beginning with the control
48 are parsed for macros. Other lines are interpreted within the scope of
50 .Bd -literal -offset indent
51 \&.SH Macro lines change control state.
52 Other lines are interpreted within the current state.
57 documents may contain only graphable 7-bit ASCII characters and the
65 Blank lines are acceptable; where found, the output will assert a
70 escape is common in historical
72 documents; if encountered at the end of a word, it ensures that the
73 subsequent word isn't off-set by whitespace.
75 .Ss Special Characters
76 Special character sequences begin with the escape character
78 followed by either an open-parenthesis
80 for two-character sequences; an open-bracket
82 for n-character sequences (terminated at a close-bracket
84 or a single one-character sequence.
86 Characters may alternatively be escaped by a slash-asterisk,
88 with the same combinations as described above. This form is deprecated.
91 Macros are one to three three characters in length and begin with a
94 at the beginning of the line. An arbitrary amount of whitespace may
95 sit between the control character and the macro name. Thus,
103 macros follow the same structural rules:
104 .Bd -literal -offset indent
105 \&.YO \(lBbody...\(rB
110 consists of zero or more arguments to the macro.
113 has a primitive notion of multi-line scope for the following macros:
127 When these macros are invoked without arguments, the subsequent line is
128 considered a continuation of the macro. Thus:
129 .Bd -literal -offset indent
136 If two consecutive lines exhibit the latter behaviour,
137 an error is raised. Thus, the following is not acceptable:
138 .Bd -literal -offset indent
146 macro is similar, but does not need an empty argument line to trigger
150 This section contains a complete list of all
152 macros and corresponding number of arguments.
154 .Bl -column "MacroX" "Arguments" -compact -offset indent
155 .It Em Macro Ta Em Arguments
178 Although not historically part of the
180 system, the following macros are also supported:
182 .Bl -column "MacroX" "Arguments" -compact -offset indent
183 .It Em Macro Ta Em Arguments
188 These follow the same calling conventions as the above
199 utility was written by
200 .An Kristaps Dzonsons Aq kristaps@openbsd.org .
203 Do not use this language. Use