1 .\" $Id: man.7,v 1.44 2009/11/02 09:53:15 kristaps Exp $
3 .\" Copyright (c) 2009 Kristaps Dzonsons <kristaps@kth.se>
5 .\" Permission to use, copy, modify, and distribute this software for any
6 .\" purpose with or without fee is hereby granted, provided that the above
7 .\" copyright notice and this permission notice appear in all copies.
9 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
10 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
11 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
12 .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
13 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
14 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
17 .Dd $Mdocdate: November 2 2009 $
24 .Nd man language reference
30 language was historically used to format
32 manuals. This reference document describes its syntax, structure, and
39 to write your manuals.
48 document follows simple rules: lines beginning with the control
51 are parsed for macros. Other lines are interpreted within the scope of
53 .Bd -literal -offset indent
54 \&.SH Macro lines change control state.
55 Other lines are interpreted within the current state.
61 documents may contain only graphable 7-bit ASCII characters, the
62 space character, and the tabs character. All manuals must have
67 Blank lines are acceptable; where found, the output will assert a
73 escape is common in historical
75 documents; if encountered at the end of a word, it ensures that the
76 subsequent word isn't off-set by whitespace.
82 whether in a macro or free-form text line, is ignored to the end of
83 line. A macro line with only a control character and comment escape,
85 is also ignored. Macro lines with only a control character and
86 optionally whitespace are stripped from input.
89 .Ss Special Characters
90 Special characters may occur in both macro and free-form lines.
91 Sequences begin with the escape character
93 followed by either an open-parenthesis
95 for two-character sequences; an open-bracket
97 for n-character sequences (terminated at a close-bracket
99 or a single one-character sequence. See
101 for a complete list. Examples include
110 Terms may be text-decorated using the
112 escape followed by an indicator: B (bold), I, (italic), or P and R
117 Unless specifically escaped, consecutive blocks of whitespace are pruned
118 from input. These are later re-added, if applicable, by a front-end
128 macro that requires a date. The form for this date is the ISO-8601
134 Many macros support scaled widths for their arguments, such as
135 stipulating a two-inch paragraph indentation with the following:
136 .Bd -literal -offset indent
141 The syntax for scaled widths is
142 .Sq Li [+-]?[0-9]*.[0-9]*[:unit:]? ,
143 where a decimal must be preceded or proceeded by at least one digit.
144 Negative numbers, while accepted, are truncated to zero. The following
145 scaling units are accepted:
148 .Bl -tag -width Ds -offset indent -compact
161 default vertical span
173 default horizontal span
178 Using anything other than
184 is necessarily non-portable across output media.
187 If a scaling unit is not provided, the numerical value is interpreted
188 under the default rules of
190 for vertical spaces and
196 which, if a unit is not provided, will instead interpret the string as
203 document must contain contains at least the
205 macro describing the document's section and title. It may occur
206 anywhere in the document, although conventionally, it appears as the
212 at least one macro or text node must appear in the document. Documents
213 are generally structured as follows:
214 .Bd -literal -offset indent
215 \&.TH FOO 1 2009-10-10
218 \efBfoo\efR \e(en a description goes here
219 \&.\e\*q The next is for sections 2 & 3 only.
223 \efBfoo\efR [\efB\e-options\efR] arguments...
226 The \efBfoo\efR utility processes files...
228 \&.\e\*q .SH IMPLEMENTATION NOTES
229 \&.\e\*q The next is for sections 1 & 8 only.
230 \&.\e\*q .SH EXIT STATUS
231 \&.\e\*q The next is for sections 2, 3, & 9 only.
232 \&.\e\*q .SH RETURN VALUES
233 \&.\e\*q The next is for sections 1, 6, 7, & 8 only.
234 \&.\e\*q .SH ENVIRONMENT
236 \&.\e\*q .SH EXAMPLES
237 \&.\e\*q The next is for sections 1, 4, 6, 7, & 8 only.
238 \&.\e\*q .SH DIAGNOSTICS
239 \&.\e\*q The next is for sections 2, 3, & 9 only.
241 \&.\e\*q .SH SEE ALSO
242 \&.\e\*q .BR foo ( 1 )
243 \&.\e\*q .SH STANDARDS
248 \&.\e\*q .SH SECURITY CONSIDERATIONS
253 document are conventionally ordered as they appear above. Sections
254 should be composed as follows:
255 .Bl -ohang -offset indent
257 The name(s) and a short description of the documented material. The
258 syntax for this is generally as follows:
260 .D1 \efBname\efR \e(en description
262 The name of the library containing the documented material, which is
263 assumed to be a function in a section 2 or 3 manual. For functions in
264 the C library, this may be as follows:
266 .D1 Standard C Library (libc, -lc)
268 Documents the utility invocation syntax, function call syntax, or device
271 For the first, utilities (sections 1, 6, and 8), this is
272 generally structured as follows:
274 .D1 \efBname\efR [-\efBab\efR] [-\efBc\efR\efIarg\efR] \efBpath\efR...
276 For the second, function calls (sections 2, 3, 9):
278 .D1 \&.B char *name(char *\efIarg\efR);
280 And for the third, configurations (section 4):
282 .D1 \&.B name* at cardbus ? function ?
284 Manuals not in these sections generally don't need a
287 This expands upon the brief, one-line description in
289 It usually contains a break-down of the options (if documenting a
291 .It Em IMPLEMENTATION NOTES
292 Implementation-specific notes should be kept here. This is useful when
293 implementing standard functions that may have side effects or notable
294 algorithmic implications.
296 Command exit status for section 1, 6, and 8 manuals. This section is
299 which is used for functions. Historically, this information was
302 a practise that is now discouraged.
305 This section is the dual of
307 which is used for commands. It documents the return values of functions
308 in sections 2, 3, and 9.
311 Documents any usages of environment variables, e.g.,
315 Documents files used. It's helpful to document both the file and a
316 short description of how the file is used (created, modified, etc.).
319 Example usages. This often contains snippets of well-formed,
320 well-tested invocations. Make doubly sure that your examples work
324 Documents error conditions. This is most useful in section 4 manuals.
325 Historically, this section was used in place of
327 for manuals in sections 1, 6, and 8; however, this practise is
331 Documents error handling in sections 2, 3, and 9.
334 References other manuals with related topics. This section should exist
337 .D1 \&.BR bar \&( 1 \&),
339 Cross-references should conventionally be ordered
340 first by section, then alphabetically.
343 References any standards implemented or used, such as
345 .D1 IEEE Std 1003.2 (\e(lqPOSIX.2\e(rq)
347 If not adhering to any standards, the
349 section should be used.
352 The history of any manual without a
354 section should be described in this section.
357 Credits to authors, if applicable, should appear in this section.
358 Authors should generally be noted by both name and an e-mail address.
361 Explanations of common misuses and misunderstandings should be explained
365 Extant bugs should be described in this section.
367 .It Em SECURITY CONSIDERATIONS
368 Documents any security precautions that operators should consider.
374 Macros are one to three three characters in length and begin with a
377 at the beginning of the line. An arbitrary amount of whitespace may
378 sit between the control character and the macro name. Thus, the
379 following are equivalent:
380 .Bd -literal -offset indent
388 macros are classified by scope: line scope or block scope. Line
389 macros are only scoped to the current line (and, in some situations,
390 the subsequent line). Block macros are scoped to the current line and
391 subsequent lines until closed by another block macro.
395 Line macros are generally scoped to the current line, with the body
396 consisting of zero or more arguments. If a macro is scoped to the next
397 line and the line arguments are empty, the next line is used instead,
398 else the general syntax is used. Thus:
399 .Bd -literal -offset indent
407 If next-line macros are invoked consecutively, only the last is used; in
408 other words, if a next-line macro is preceded by a block macro, it is
410 .Bd -literal -offset indent
411 \&.YO \(lBbody...\(rB
416 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "ScopeXXXXX"
417 .It Em Macro Ta Em Arguments Ta Em Scope
418 .It Sx \&B Ta n Ta next-line
419 .It Sx \&BI Ta n Ta current
420 .It Sx \&BR Ta n Ta current
421 .It Sx \&DT Ta 0 Ta current
422 .It Sx \&I Ta n Ta next-line
423 .It Sx \&IB Ta n Ta current
424 .It Sx \&IR Ta n Ta current
425 .It Sx \&PD Ta n Ta current
426 .It Sx \&R Ta n Ta next-line
427 .It Sx \&RB Ta n Ta current
428 .It Sx \&RI Ta n Ta current
429 .It Sx \&SB Ta n Ta next-line
430 .It Sx \&SM Ta n Ta next-line
431 .It Sx \&TH Ta >1, <6 Ta current
432 .It Sx \&UC Ta n Ta current
433 .It Sx \&br Ta 0 Ta current
434 .It Sx \&fi Ta 0 Ta current
435 .It Sx \&i Ta n Ta current
436 .It Sx \&na Ta 0 Ta current
437 .It Sx \&nf Ta 0 Ta current
438 .It Sx \&r Ta 0 Ta current
439 .It Sx \&sp Ta 1 Ta current
456 macros should not be used. They're included for compatibility.
460 Block macros are comprised of a head and body. Like for in-line macros,
461 the head is scoped to the current line and, in one circumstance, the
462 next line; the body is scoped to subsequent lines and is closed out by a
463 subsequent block macro invocation.
464 .Bd -literal -offset indent
465 \&.YO \(lBhead...\(rB
471 The closure of body scope may be to the section, where a macro is closed
474 sub-section, closed by a section or
476 part, closed by a section, sub-section, or
478 or paragraph, closed by a section, sub-section, part,
486 No closure refers to an explicit block closing macro.
489 .Bl -column "MacroX" "ArgumentsX" "Head ScopeX" "sub-sectionX" -compact -offset indent
490 .It Em Macro Ta Em Arguments Ta Em Head Scope Ta Em Body Scope
491 .It Sx \&HP Ta <2 Ta current Ta paragraph
492 .It Sx \&IP Ta <3 Ta current Ta paragraph
493 .It Sx \&LP Ta 0 Ta current Ta paragraph
494 .It Sx \&P Ta 0 Ta current Ta paragraph
495 .It Sx \&PP Ta 0 Ta current Ta paragraph
496 .It Sx \&RE Ta 0 Ta current Ta none
497 .It Sx \&RS Ta 1 Ta current Ta part
498 .It Sx \&SH Ta >0 Ta next-line Ta section
499 .It Sx \&SS Ta >0 Ta next-line Ta sub-section
500 .It Sx \&TP Ta n Ta next-line Ta paragraph
504 If a block macro is next-line scoped, it may only be followed by in-line
519 This section is a canonical reference to all macros, arranged
520 alphabetically. For the scoping of individual macros, see
525 Text is rendered in bold face.
537 Text is rendered alternately in bold face and italic. Thus,
538 .Sq .BI this word and that
543 to render in bold face, while
547 render in italics. Whitespace between arguments is omitted in output.
550 .Bd -filled -offset indent
552 bold italic bold italic
555 The output of this example will be emboldened
559 with spaces stripped between arguments.
571 Text is rendered alternately in bold face and roman (the default font).
572 Whitespace between arguments is omitted in output.
576 for an equivalent example.
588 Has no effect. Included for compatibility.
592 Begin a paragraph whose initial output line is left-justified, but
593 subsequent output lines are indented, with the following syntax:
594 .Bd -filled -offset indent
601 argument must conform to
603 If specified, it's saved for later paragraph left-margins; if unspecified, the
604 saved or default width is used.
616 Text is rendered in italics.
628 Text is rendered alternately in italics and bold face. Whitespace
629 between arguments is omitted in output.
633 for an equivalent example.
645 Begin an indented paragraph with the following syntax:
646 .Bd -filled -offset indent
648 .Op Cm head Op Cm width
653 argument defines the width of the left margin and is defined by
655 It's saved for later paragraph left-margins; if unspecified, the saved or
656 default width is used.
660 argument is used as a leading term, flushed to the left margin. This is
661 useful for bulleted paragraphs and so on.
673 Text is rendered alternately in italics and roman (the default font).
674 Whitespace between arguments is omitted in output.
678 for an equivalent example.
690 Begin an undecorated paragraph. The scope of a paragraph is closed by a
691 subsequent paragraph, sub-section, section, or end of file. The saved
692 paragraph left-margin width is re-set to the default.
730 Text is rendered in roman (the default font).
742 Text is rendered alternately in roman (the default font) and bold face.
743 Whitespace between arguments is omitted in output.
747 for an equivalent example.
759 Explicitly close out the scope of a prior
764 Text is rendered alternately in roman (the default font) and italics.
765 Whitespace between arguments is omitted in output.
769 for an equivalent example.
781 Begin a part setting the left margin. The left margin controls the
782 offset, following an initial indentation, to un-indented text such as
785 This has the following syntax:
786 .Bd -filled -offset indent
793 argument must conform to
795 If not specified, the saved or default width is used.
799 Text is rendered in small size (one point smaller than the default font)
804 Begin a section. The scope of a section is only closed by another
805 section or the end of file. The paragraph left-margin width is re-set
810 Text is rendered in small size (one point smaller than the default
815 Begin a sub-section. The scope of a sub-section is closed by a
816 subsequent sub-section, section, or end of file. The paragraph
817 left-margin width is re-set to the default.
821 Sets the title of the manual page with the following syntax:
822 .Bd -filled -offset indent
825 .Op Cm date Op Cm source Op Cm volume
828 At least the upper-case document title
830 and numeric manual section
832 arguments must be provided. The
834 argument should be formatted as described in
836 if it does not conform, the current date is used instead. The
838 string specifies the organisation providing the utility. The
840 string replaces the default rendered volume, which is dictated by the
844 .Bd -filled -offset indent
845 \&.TH CVS 5 "1992-02-12" GNU
850 Begin a paragraph where the head, if exceeding the indentation width, is
851 followed by a newline; if not, the body follows on the same line after a
852 buffer to the indentation width. Subsequent output lines are indented.
853 The syntax is as follows:
854 .Bd -filled -offset indent
861 argument must conform to
863 If specified, it's saved for later paragraph left-margins; if
864 unspecified, the saved or default width is used.
876 Has no effect. Included for compatibility.
880 Has no effect. Included for compatibility.
884 Breaks the current line. Consecutive invocations have no further effect.
891 End literal mode begun by
896 Italicise arguments. If no arguments are specified, all subsequent text
909 Don't align to the right margin.
913 Begin literal mode: all subsequent free-form lines have their end of
914 line boundaries preserved. May be ended by
919 Fonts and styles (bold face, italics) reset to roman (default font).
931 Insert vertical spaces into output with the following syntax:
932 .Bd -filled -offset indent
939 spaces, which must conform to
941 If 0, this is equivalent to the
943 macro. Defaults to 1, if unspecified.
950 This section documents compatibility with other roff implementations, at
955 In quoted literals, groff allowed pair-wise double-quotes to produce a
956 standalone double-quote in formatted output. This idiosyncratic
957 behaviour is no longer applicable.
961 macro does not accept negative numbers.
963 Blocks of whitespace are stripped from both macro and free-form text
964 lines (except when in literal mode), while groff would retain whitespace
965 in free-form text lines.
977 reference was written by
978 .An Kristaps Dzonsons Aq kristaps@kth.se .
982 Do not use this language. Use