1 .\" $Id: man.7,v 1.71 2010/05/15 07:01:51 kristaps Exp $
3 .\" Copyright (c) 2009 Kristaps Dzonsons <kristaps@bsd.lv>
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: May 15 2010 $
22 .Nd man language reference
26 language was historically used to format
29 This reference document describes its syntax, structure, and usage.
34 to write your manuals.
42 document follows simple rules: lines beginning with the control
45 are parsed for macros.
46 Other lines are interpreted within the scope of
48 .Bd -literal -offset indent
49 \&.SH Macro lines change control state.
50 Other lines are interpreted within the current state.
54 documents may contain only graphable 7-bit ASCII characters, the
55 space character, and the tabs character.
60 Blank lines are acceptable; where found, the output will assert a
65 whether in a macro or free-form text line, is ignored to the end of
67 A macro line with only a control character and comment escape,
70 Macro lines with only a control character and optionally whitespace are
72 .Ss Special Characters
73 Special characters may occur in both macro and free-form lines.
74 Sequences begin with the escape character
76 followed by either an open-parenthesis
78 for two-character sequences; an open-bracket
80 for n-character sequences (terminated at a close-bracket
82 or a single one-character sequence.
93 Terms may be text-decorated using the
95 escape followed by an indicator: B (bold), I, (italic), R (Roman), or P
96 (revert to previous mode):
98 .D1 \efBbold\efR \efIitalic\efP
100 A numerical representation 3, 2, or 1 (bold, italic, and Roman,
101 respectively) may be used instead.
102 A text decoration is only valid, if specified in free-form text, until
103 the next macro invocation; if specified within a macro, it's only valid
104 until the macro closes scope.
105 Note that macros like
107 open and close a font scope with each argument.
109 Text may also be sized with the
111 escape, whose syntax is one of
113 for one-digit numerals;
117 for two-digit numerals; and
123 for arbitrary-digit numerals:
126 .D1 \es[+10]much bigger\es[-10]
127 .D1 \es+(10much bigger\es-(10
128 .D1 \es+'100'much much bigger\es-'100'
134 attributes are forgotten when entering or exiting a macro block.
136 Whitespace consists of the space character.
137 In free-form lines, whitespace is preserved within a line; un-escaped
138 trailing spaces are stripped from input (unless in a literal context).
139 Blank free-form lines, which may include spaces, are permitted and
140 rendered as an empty line.
142 In macro lines, whitespace delimits arguments and is discarded.
143 If arguments are quoted, whitespace within the quotes is retained.
149 macro that requires a date.
150 The form for this date is the ISO-8601
154 Many macros support scaled widths for their arguments, such as
155 stipulating a two-inch paragraph indentation with the following:
156 .Bd -literal -offset indent
160 The syntax for scaled widths is
161 .Sq Li [+-]?[0-9]*.[0-9]*[:unit:]? ,
162 where a decimal must be preceded or proceeded by at least one digit.
163 Negative numbers, while accepted, are truncated to zero.
164 The following scaling units are accepted:
166 .Bl -tag -width Ds -offset indent -compact
179 default vertical span
191 default horizontal span
196 Using anything other than
202 is necessarily non-portable across output media.
204 If a scaling unit is not provided, the numerical value is interpreted
205 under the default rules of
207 for vertical spaces and
213 which, if a unit is not provided, will instead interpret the string as
216 When composing a manual, make sure that your sentences end at the end of
218 By doing so, front-ends will be able to apply the proper amount of
219 spacing after the end of sentence (unescaped) period, exclamation mark,
220 or question mark followed by zero or more non-sentence closing
229 document must contain contains at least the
231 macro describing the document's section and title.
232 It may occur anywhere in the document, although conventionally, it
233 appears as the first macro.
237 at least one macro or text node must appear in the document.
238 Documents are generally structured as follows:
239 .Bd -literal -offset indent
240 \&.TH FOO 1 2009-10-10
243 \efBfoo\efR \e(en a description goes here
244 \&.\e\*q The next is for sections 2 & 3 only.
248 \efBfoo\efR [\efB\e-options\efR] arguments...
251 The \efBfoo\efR utility processes files...
253 \&.\e\*q .SH IMPLEMENTATION NOTES
254 \&.\e\*q The next is for sections 2, 3, & 9 only.
255 \&.\e\*q .SH RETURN VALUES
256 \&.\e\*q The next is for sections 1, 6, 7, & 8 only.
257 \&.\e\*q .SH ENVIRONMENT
259 \&.\e\*q The next is for sections 1 & 8 only.
260 \&.\e\*q .SH EXIT STATUS
261 \&.\e\*q .SH EXAMPLES
262 \&.\e\*q The next is for sections 1, 4, 6, 7, & 8 only.
263 \&.\e\*q .SH DIAGNOSTICS
264 \&.\e\*q The next is for sections 2, 3, & 9 only.
266 \&.\e\*q .SH SEE ALSO
267 \&.\e\*q .BR foo ( 1 )
268 \&.\e\*q .SH STANDARDS
273 \&.\e\*q .SH SECURITY CONSIDERATIONS
278 document are conventionally ordered as they appear above.
279 Sections should be composed as follows:
280 .Bl -ohang -offset indent
282 The name(s) and a short description of the documented material.
283 The syntax for this is generally as follows:
285 .D1 \efBname\efR \e(en description
287 The name of the library containing the documented material, which is
288 assumed to be a function in a section 2 or 3 manual.
289 For functions in the C library, this may be as follows:
291 .D1 Standard C Library (libc, -lc)
293 Documents the utility invocation syntax, function call syntax, or device
296 For the first, utilities (sections 1, 6, and 8), this is
297 generally structured as follows:
299 .D1 \efBname\efR [-\efBab\efR] [-\efBc\efR\efIarg\efR] \efBpath\efR...
301 For the second, function calls (sections 2, 3, 9):
303 .D1 \&.B char *name(char *\efIarg\efR);
305 And for the third, configurations (section 4):
307 .D1 \&.B name* at cardbus ? function ?
309 Manuals not in these sections generally don't need a
312 This expands upon the brief, one-line description in
314 It usually contains a break-down of the options (if documenting a
316 .It Em IMPLEMENTATION NOTES
317 Implementation-specific notes should be kept here.
318 This is useful when implementing standard functions that may have side
319 effects or notable algorithmic implications.
321 This section is the dual of
323 which is used for commands.
324 It documents the return values of functions in sections 2, 3, and 9.
326 Documents any usages of environment variables, e.g.,
329 Documents files used.
330 It's helpful to document both the file and a short description of how
331 the file is used (created, modified, etc.).
333 Command exit status for section 1, 6, and 8 manuals.
334 This section is the dual of
336 which is used for functions.
337 Historically, this information was described in
339 a practise that is now discouraged.
342 This often contains snippets of well-formed,
343 well-tested invocations.
344 Make doubly sure that your examples work properly!
346 Documents error conditions.
347 This is most useful in section 4 manuals.
348 Historically, this section was used in place of
350 for manuals in sections 1, 6, and 8; however, this practise is
353 Documents error handling in sections 2, 3, and 9.
355 References other manuals with related topics.
356 This section should exist for most manuals.
358 .D1 \&.BR bar \&( 1 \&),
360 Cross-references should conventionally be ordered
361 first by section, then alphabetically.
363 References any standards implemented or used, such as
365 .D1 IEEE Std 1003.2 (\e(lqPOSIX.2\e(rq)
367 If not adhering to any standards, the
369 section should be used.
371 The history of any manual without a
373 section should be described in this section.
375 Credits to authors, if applicable, should appear in this section.
376 Authors should generally be noted by both name and an e-mail address.
378 Explanations of common misuses and misunderstandings should be explained
381 Extant bugs should be described in this section.
382 .It Em SECURITY CONSIDERATIONS
383 Documents any security precautions that operators should consider.
386 Macros are one to three three characters in length and begin with a
389 at the beginning of the line.
392 macro control character is also accepted.
393 An arbitrary amount of whitespace (spaces or tabs) may sit between the
394 control character and the macro name.
395 Thus, the following are equivalent:
396 .Bd -literal -offset indent
403 macros are classified by scope: line scope or block scope.
404 Line macros are only scoped to the current line (and, in some
405 situations, the subsequent line).
406 Block macros are scoped to the current line and subsequent lines until
407 closed by another block macro.
409 Line macros are generally scoped to the current line, with the body
410 consisting of zero or more arguments.
411 If a macro is scoped to the next line and the line arguments are empty,
412 the next line, which must be text, is used instead.
414 .Bd -literal -offset indent
421 If next-line macros are invoked consecutively, only the last is used.
422 If a next-line macro is followed by a non-next-line macro, an error is
423 raised (unless in the case of
429 The syntax is as follows:
430 .Bd -literal -offset indent
431 \&.YO \(lBbody...\(rB
435 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "ScopeXXXXX" "CompatX"
436 .It Em Macro Ta Em Arguments Ta Em Scope Ta Em Notes
437 .It Sx \&B Ta n Ta next-line Ta \&
438 .It Sx \&BI Ta n Ta current Ta \&
439 .It Sx \&BR Ta n Ta current Ta \&
440 .It Sx \&DT Ta 0 Ta current Ta \&
441 .It Sx \&I Ta n Ta next-line Ta \&
442 .It Sx \&IB Ta n Ta current Ta \&
443 .It Sx \&IR Ta n Ta current Ta \&
444 .\" .It Sx \&PD Ta n Ta current Ta compat
445 .It Sx \&R Ta n Ta next-line Ta \&
446 .It Sx \&RB Ta n Ta current Ta \&
447 .It Sx \&RI Ta n Ta current Ta \&
448 .It Sx \&SB Ta n Ta next-line Ta \&
449 .It Sx \&SM Ta n Ta next-line Ta \&
450 .It Sx \&TH Ta >1, <6 Ta current Ta \&
451 .\" .It Sx \&UC Ta n Ta current Ta compat
452 .It Sx \&br Ta 0 Ta current Ta compat
453 .It Sx \&fi Ta 0 Ta current Ta compat
454 .It Sx \&i Ta n Ta current Ta compat
455 .It Sx \&na Ta 0 Ta current Ta compat
456 .It Sx \&nf Ta 0 Ta current Ta compat
457 .It Sx \&r Ta 0 Ta current Ta compat
458 .It Sx \&sp Ta 1 Ta current Ta compat
459 .\" .It Sx \&Sp Ta <1 Ta current Ta compat
460 .\" .It Sx \&Vb Ta <1 Ta current Ta compat
461 .\" .It Sx \&Ve Ta 0 Ta current Ta compat
466 are included for compatibility with the significant corpus of existing
467 manuals that mix dialects of roff.
468 These macros should not be used for portable
472 Block macros are comprised of a head and body.
473 Like for in-line macros, the head is scoped to the current line and, in
474 one circumstance, the next line (the next-line stipulations as in
478 The syntax is as follows:
479 .Bd -literal -offset indent
480 \&.YO \(lBhead...\(rB
485 The closure of body scope may be to the section, where a macro is closed
488 sub-section, closed by a section or
490 part, closed by a section, sub-section, or
492 or paragraph, closed by a section, sub-section, part,
500 No closure refers to an explicit block closing macro.
502 As a rule, block macros may not be nested; thus, calling a block macro
503 while another block macro scope is open, and the open scope is not
504 implicitly closed, is syntactically incorrect.
506 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "Head ScopeX" "sub-sectionX" "compatX"
507 .It Em Macro Ta Em Arguments Ta Em Head Scope Ta Em Body Scope Ta Em Notes
508 .It Sx \&HP Ta <2 Ta current Ta paragraph Ta \&
509 .It Sx \&IP Ta <3 Ta current Ta paragraph Ta \&
510 .It Sx \&LP Ta 0 Ta current Ta paragraph Ta \&
511 .It Sx \&P Ta 0 Ta current Ta paragraph Ta \&
512 .It Sx \&PP Ta 0 Ta current Ta paragraph Ta \&
513 .It Sx \&RE Ta 0 Ta current Ta none Ta compat
514 .It Sx \&RS Ta 1 Ta current Ta part Ta compat
515 .It Sx \&SH Ta >0 Ta next-line Ta section Ta \&
516 .It Sx \&SS Ta >0 Ta next-line Ta sub-section Ta \&
517 .It Sx \&TP Ta n Ta next-line Ta paragraph Ta \&
525 If a block macro is next-line scoped, it may only be followed by in-line
526 macros for decorating text.
528 This section is a canonical reference to all macros, arranged
530 For the scoping of individual macros, see
533 Text is rendered in bold face.
543 Text is rendered alternately in bold face and italic.
545 .Sq .BI this word and that
550 to render in bold face, while
555 Whitespace between arguments is omitted in output.
559 .D1 \&.BI bold italic bold italic
561 The output of this example will be emboldened
565 with spaces stripped between arguments.
575 Text is rendered alternately in bold face and roman (the default font).
576 Whitespace between arguments is omitted in output.
580 for an equivalent example.
591 Included for compatibility.
593 Begin a paragraph whose initial output line is left-justified, but
594 subsequent output lines are indented, with the following syntax:
595 .Bd -filled -offset indent
602 argument must conform to
604 If specified, it's saved for later paragraph left-margins; if unspecified, the
605 saved or default width is used.
615 Text is rendered in italics.
625 Text is rendered alternately in italics and bold face. Whitespace
626 between arguments is omitted in output.
630 for an equivalent example.
640 Begin an indented paragraph with the following syntax:
641 .Bd -filled -offset indent
643 .Op Cm head Op Cm width
648 argument defines the width of the left margin and is defined by
650 It's saved for later paragraph left-margins; if unspecified, the saved or
651 default width is used.
655 argument is used as a leading term, flushed to the left margin.
656 This is useful for bulleted paragraphs and so on.
666 Text is rendered alternately in italics and roman (the default font).
667 Whitespace between arguments is omitted in output.
671 for an equivalent example.
681 Begin an undecorated paragraph.
682 The scope of a paragraph is closed by a subsequent paragraph,
683 sub-section, section, or end of file.
684 The saved paragraph left-margin width is re-set to the default.
716 Text is rendered in roman (the default font).
726 Text is rendered alternately in roman (the default font) and bold face.
727 Whitespace between arguments is omitted in output.
731 for an equivalent example.
741 Explicitly close out the scope of a prior
744 Text is rendered alternately in roman (the default font) and italics.
745 Whitespace between arguments is omitted in output.
749 for an equivalent example.
759 Begin a part setting the left margin.
760 The left margin controls the offset, following an initial indentation,
761 to un-indented text such as that of
763 This has the following syntax:
764 .Bd -filled -offset indent
771 argument must conform to
773 If not specified, the saved or default width is used.
775 Text is rendered in small size (one point smaller than the default font)
779 The scope of a section is only closed by another section or the end of
781 The paragraph left-margin width is re-set to the default.
783 Text is rendered in small size (one point smaller than the default
787 The scope of a sub-section is closed by a subsequent sub-section,
788 section, or end of file.
789 The paragraph left-margin width is re-set to the default.
791 Sets the title of the manual page with the following syntax:
792 .Bd -filled -offset indent
795 .Op Cm date Op Cm source Op Cm volume
798 At least the upper-case document title
800 and numeric manual section
802 arguments must be provided.
805 argument should be formatted as described in
807 if it does not conform, the current date is used instead.
810 string specifies the organisation providing the utility.
813 string replaces the default rendered volume, which is dictated by the
818 .D1 \&.TH CVS 5 "1992-02-12" GNU
820 Begin a paragraph where the head, if exceeding the indentation width, is
821 followed by a newline; if not, the body follows on the same line after a
822 buffer to the indentation width.
823 Subsequent output lines are indented.
824 The syntax is as follows:
825 .Bd -filled -offset indent
832 argument must conform to
834 If specified, it's saved for later paragraph left-margins; if
835 unspecified, the saved or default width is used.
847 .\" Has no effect. Included for compatibility.
851 .\" Has no effect. Included for compatibility.
853 Breaks the current line.
854 Consecutive invocations have no further effect.
859 End literal mode begun by
874 Don't align to the right margin.
876 Begin literal mode: all subsequent free-form lines have their end of
877 line boundaries preserved.
881 Fonts and styles (bold face, italics) reset to roman (default font).
891 Insert vertical spaces into output with the following syntax:
892 .Bd -filled -offset indent
899 spaces, which must conform to
901 If 0, this is equivalent to the
904 Defaults to 1, if unspecified.
916 .\" Accepts an argument (the height of the formatted space) which is
924 This section documents areas of questionable portability between
925 implementations of the
931 In quoted literals, GNU troff allowed pair-wise double-quotes to produce
932 a standalone double-quote in formatted output.
933 It is not known whether this behaviour is exhibited by other formatters.
937 macro does not accept negative values in mandoc.
938 In GNU troff, this would result in strange behaviour.
942 macro control character, in GNU troff (and prior troffs) suppresses a
943 newline before macro output; in mandoc, it is an alias for the standard
953 reference was written by
954 .An Kristaps Dzonsons Aq kristaps@bsd.lv .
956 Do not use this language.