1 .\" $Id: man.7,v 1.80 2010/07/26 10:00:03 kristaps Exp $
3 .\" Copyright (c) 2009, 2010 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: July 26 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 tab 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.
111 attribute is forgotten when entering or exiting a macro block.
113 Whitespace consists of the space character.
114 In free-form lines, whitespace is preserved within a line; unescaped
115 trailing spaces are stripped from input (unless in a literal context).
116 Blank free-form lines, which may include spaces, are permitted and
117 rendered as an empty line.
119 In macro lines, whitespace delimits arguments and is discarded.
120 If arguments are quoted, whitespace within the quotes is retained.
126 macro that requires a date.
127 The form for this date is the ISO-8601
131 Many macros support scaled widths for their arguments, such as
132 stipulating a two-inch paragraph indentation with the following:
133 .Bd -literal -offset indent
137 The syntax for scaled widths is
138 .Sq Li [+-]?[0-9]*.[0-9]*[:unit:]? ,
139 where a decimal must be preceded or proceeded by at least one digit.
140 Negative numbers, while accepted, are truncated to zero.
141 The following scaling units are accepted:
143 .Bl -tag -width Ds -offset indent -compact
156 default vertical span
168 default horizontal span
173 Using anything other than
179 is necessarily non-portable across output media.
181 If a scaling unit is not provided, the numerical value is interpreted
182 under the default rules of
184 for vertical spaces and
190 which, if a unit is not provided, will instead interpret the string as
193 When composing a manual, make sure that sentences end at the end of
195 By doing so, front-ends will be able to apply the proper amount of
196 spacing after the end of sentence (unescaped) period, exclamation mark,
197 or question mark followed by zero or more non-sentence closing
208 document must contain the
210 macro describing the document's section and title.
211 It may occur anywhere in the document, although conventionally it
212 appears as the first macro.
216 at least one macro or text node must appear in the document.
217 Documents are generally structured as follows:
218 .Bd -literal -offset indent
219 \&.TH FOO 1 2009-10-10
221 \efBfoo\efR \e(en a description goes here
222 \&.\e\*q The next is for sections 2 & 3 only.
225 \efBfoo\efR [\efB\e-options\efR] arguments...
227 The \efBfoo\efR utility processes files...
228 \&.\e\*q .SH IMPLEMENTATION NOTES
229 \&.\e\*q The next is for sections 2, 3, & 9 only.
230 \&.\e\*q .SH RETURN VALUES
231 \&.\e\*q The next is for sections 1, 6, 7, & 8 only.
232 \&.\e\*q .SH ENVIRONMENT
234 \&.\e\*q The next is for sections 1 & 8 only.
235 \&.\e\*q .SH EXIT STATUS
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.
254 Sections should be composed as follows:
255 .Bl -ohang -offset indent
257 The name(s) and a short description of the documented material.
258 The 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.
264 For functions in 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.
293 This is useful when implementing standard functions that may have side
294 effects or notable algorithmic implications.
296 This section documents the return values of functions in sections 2, 3, and 9.
298 Documents any usages of environment variables, e.g.,
301 Documents files used.
302 It's helpful to document both the file name and a short description of how
303 the file is used (created, modified, etc.).
305 This section documents the command exit status for
306 section 1, 6, and 8 utilities.
307 Historically, this information was described in
309 a practise that is now discouraged.
312 This often contains snippets of well-formed,
313 well-tested invocations.
314 Make sure that examples work properly!
316 Documents error conditions.
317 This is most useful in section 4 manuals.
318 Historically, this section was used in place of
320 for manuals in sections 1, 6, and 8; however, this practise is
323 Documents error handling in sections 2, 3, and 9.
325 References other manuals with related topics.
326 This section should exist for most manuals.
328 .D1 \&.BR bar \&( 1 \&),
330 Cross-references should conventionally be ordered
331 first by section, then alphabetically.
333 References any standards implemented or used, such as
335 .D1 IEEE Std 1003.2 (\e(lqPOSIX.2\e(rq)
337 If not adhering to any standards, the
339 section should be used.
341 The history of any manual without a
343 section should be described in this section.
345 Credits to authors, if applicable, should appear in this section.
346 Authors should generally be noted by both name and email address.
348 Common misuses and misunderstandings should be explained
351 Known bugs, limitations, and work-arounds should be described
353 .It Em SECURITY CONSIDERATIONS
354 Documents any security precautions that operators should consider.
357 Macros are one to three characters in length and begin with a
360 at the beginning of the line.
363 macro control character is also accepted.
364 An arbitrary amount of whitespace (spaces or tabs) may sit between the
365 control character and the macro name.
366 Thus, the following are equivalent:
367 .Bd -literal -offset indent
374 macros are classified by scope: line scope or block scope.
375 Line macros are only scoped to the current line (and, in some
376 situations, the subsequent line).
377 Block macros are scoped to the current line and subsequent lines until
378 closed by another block macro.
380 Line macros are generally scoped to the current line, with the body
381 consisting of zero or more arguments.
382 If a macro is scoped to the next line and the line arguments are empty,
383 the next line, which must be text, is used instead.
385 .Bd -literal -offset indent
392 If next-line macros are invoked consecutively, only the last is used.
393 If a next-line macro is followed by a non-next-line macro, an error is
400 The syntax is as follows:
401 .Bd -literal -offset indent
402 \&.YO \(lBbody...\(rB
406 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "ScopeXXXXX" "CompatX"
407 .It Em Macro Ta Em Arguments Ta Em Scope Ta Em Notes
408 .It Sx \&AT Ta <=1 Ta current Ta \&
409 .It Sx \&B Ta n Ta next-line Ta \&
410 .It Sx \&BI Ta n Ta current Ta \&
411 .It Sx \&BR Ta n Ta current Ta \&
412 .It Sx \&DT Ta 0 Ta current Ta \&
413 .It Sx \&I Ta n Ta next-line Ta \&
414 .It Sx \&IB Ta n Ta current Ta \&
415 .It Sx \&IR Ta n Ta current Ta \&
416 .\" .It Sx \&PD Ta n Ta current Ta compat
417 .It Sx \&R Ta n Ta next-line Ta \&
418 .It Sx \&RB Ta n Ta current Ta \&
419 .It Sx \&RI Ta n Ta current Ta \&
420 .It Sx \&SB Ta n Ta next-line Ta \&
421 .It Sx \&SM Ta n Ta next-line Ta \&
422 .It Sx \&TH Ta >1, <6 Ta current Ta \&
423 .It Sx \&UC Ta <=1 Ta current Ta \&
424 .It Sx \&br Ta 0 Ta current Ta compat
425 .It Sx \&fi Ta 0 Ta current Ta compat
426 .It Sx \&i Ta n Ta current Ta compat
427 .It Sx \&in Ta 1 Ta current Ta compat
428 .It Sx \&na Ta 0 Ta current Ta compat
429 .It Sx \&nf Ta 0 Ta current Ta compat
430 .It Sx \&r Ta 0 Ta current Ta compat
431 .It Sx \&sp Ta 1 Ta current Ta compat
432 .\" .It Sx \&Sp Ta <1 Ta current Ta compat
433 .\" .It Sx \&Vb Ta <1 Ta current Ta compat
434 .\" .It Sx \&Ve Ta 0 Ta current Ta compat
439 are included for compatibility with the significant corpus of existing
440 manuals that mix dialects of roff.
441 These macros should not be used for portable
445 Block macros comprise a head and body.
446 As with in-line macros, the head is scoped to the current line and, in
447 one circumstance, the next line (the next-line stipulations as in
451 The syntax is as follows:
452 .Bd -literal -offset indent
453 \&.YO \(lBhead...\(rB
458 The closure of body scope may be to the section, where a macro is closed
461 sub-section, closed by a section or
463 part, closed by a section, sub-section, or
465 or paragraph, closed by a section, sub-section, part,
473 No closure refers to an explicit block closing macro.
475 As a rule, block macros may not be nested; thus, calling a block macro
476 while another block macro scope is open, and the open scope is not
477 implicitly closed, is syntactically incorrect.
479 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "Head ScopeX" "sub-sectionX" "compatX"
480 .It Em Macro Ta Em Arguments Ta Em Head Scope Ta Em Body Scope Ta Em Notes
481 .It Sx \&HP Ta <2 Ta current Ta paragraph Ta \&
482 .It Sx \&IP Ta <3 Ta current Ta paragraph Ta \&
483 .It Sx \&LP Ta 0 Ta current Ta paragraph Ta \&
484 .It Sx \&P Ta 0 Ta current Ta paragraph Ta \&
485 .It Sx \&PP Ta 0 Ta current Ta paragraph Ta \&
486 .It Sx \&RE Ta 0 Ta current Ta none Ta compat
487 .It Sx \&RS Ta 1 Ta current Ta part Ta compat
488 .It Sx \&SH Ta >0 Ta next-line Ta section Ta \&
489 .It Sx \&SS Ta >0 Ta next-line Ta sub-section Ta \&
490 .It Sx \&TP Ta n Ta next-line Ta paragraph Ta \&
498 If a block macro is next-line scoped, it may only be followed by in-line
499 macros for decorating text.
501 This section is a canonical reference to all macros, arranged
503 For the scoping of individual macros, see
506 Sets the volume for the footer for compatibility with man pages from
509 The optional arguments specify which release it is from.
511 Text is rendered in bold face.
521 Text is rendered alternately in bold face and italic.
523 .Sq .BI this word and that
528 to render in bold face, while
533 Whitespace between arguments is omitted in output.
537 .D1 \&.BI bold italic bold italic
539 The output of this example will be emboldened
543 with spaces stripped between arguments.
553 Text is rendered alternately in bold face and roman (the default font).
554 Whitespace between arguments is omitted in output.
558 for an equivalent example.
569 Included for compatibility.
571 Begin a paragraph whose initial output line is left-justified, but
572 subsequent output lines are indented, with the following syntax:
573 .Bd -filled -offset indent
580 argument must conform to
582 If specified, it's saved for later paragraph left-margins; if unspecified, the
583 saved or default width is used.
593 Text is rendered in italics.
603 Text is rendered alternately in italics and bold face.
604 Whitespace between arguments is omitted in output.
608 for an equivalent example.
618 Begin an indented paragraph with the following syntax:
619 .Bd -filled -offset indent
621 .Op Cm head Op Cm width
626 argument defines the width of the left margin and is defined by
628 It's saved for later paragraph left-margins; if unspecified, the saved or
629 default width is used.
633 argument is used as a leading term, flushed to the left margin.
634 This is useful for bulleted paragraphs and so on.
644 Text is rendered alternately in italics and roman (the default font).
645 Whitespace between arguments is omitted in output.
649 for an equivalent example.
659 Begin an undecorated paragraph.
660 The scope of a paragraph is closed by a subsequent paragraph,
661 sub-section, section, or end of file.
662 The saved paragraph left-margin width is reset to the default.
694 Text is rendered in roman (the default font).
704 Text is rendered alternately in roman (the default font) and bold face.
705 Whitespace between arguments is omitted in output.
709 for an equivalent example.
719 Explicitly close out the scope of a prior
722 Text is rendered alternately in roman (the default font) and italics.
723 Whitespace between arguments is omitted in output.
727 for an equivalent example.
737 Begin a part setting the left margin.
738 The left margin controls the offset, following an initial indentation,
739 to un-indented text such as that of
741 This has the following syntax:
742 .Bd -filled -offset indent
749 argument must conform to
751 If not specified, the saved or default width is used.
753 Text is rendered in small size (one point smaller than the default font)
757 The scope of a section is only closed by another section or the end of
759 The paragraph left-margin width is reset to the default.
761 Text is rendered in small size (one point smaller than the default
765 The scope of a sub-section is closed by a subsequent sub-section,
766 section, or end of file.
767 The paragraph left-margin width is reset to the default.
769 Sets the title of the manual page with the following syntax:
770 .Bd -filled -offset indent
773 .Op Cm date Op Cm source Op Cm volume
776 At least the upper-case document
780 arguments must be provided.
783 argument should be formatted as described in
785 but will be printed verbatim if it is not.
786 If the date is not specified, the current date is used.
789 string specifies the organisation providing the utility.
792 string replaces the default rendered volume, which is dictated by the
797 .D1 \&.TH CVS 5 "1992-02-12" GNU
799 Begin a paragraph where the head, if exceeding the indentation width, is
800 followed by a newline; if not, the body follows on the same line after a
801 buffer to the indentation width.
802 Subsequent output lines are indented.
803 The syntax is as follows:
804 .Bd -filled -offset indent
811 argument must conform to
813 If specified, it's saved for later paragraph left-margins; if
814 unspecified, the saved or default width is used.
826 .\" Has no effect. Included for compatibility.
830 Sets the volume for the footer for compatibility with man pages from
832 The optional first argument specifies which release it is from.
834 Breaks the current line.
835 Consecutive invocations have no further effect.
840 End literal mode begun by
855 Indent relative to the current indentation:
857 .D1 Pf \. Sx \&in Op Cm width
861 is signed, the new offset is relative.
862 Otherwise, it is absolute.
863 This value is reset upon the next paragraph, section, or sub-section.
865 Don't align to the right margin.
867 Begin literal mode: all subsequent free-form lines have their end of
868 line boundaries preserved.
872 Fonts and styles (bold face, italics) reset to roman (default font).
882 Insert vertical spaces into output with the following syntax:
883 .Bd -filled -offset indent
890 spaces, which must conform to
892 If 0, this is equivalent to the
895 Defaults to 1, if unspecified.
907 .\" Accepts an argument (the height of the formatted space) which is
915 This section documents areas of questionable portability between
916 implementations of the
922 The \es (font size), \em (font colour), and \eM (font filling colour)
923 font decoration escapes are all discarded in mandoc.
925 In quoted literals, GNU troff allowed pair-wise double-quotes to produce
926 a standalone double-quote in formatted output.
927 It is not known whether this behaviour is exhibited by other formatters.
931 macro does not accept negative values in mandoc.
932 In GNU troff, this would result in strange behaviour.
936 macro control character, in GNU troff (and prior troffs) suppresses a
937 newline before macro output; in mandoc, it is an alias for the standard
947 language first appeared as a macro package for the roff typesetting
950 It was later rewritten by James Clark as a macro package for groff.
951 The stand-alone implementation that is part of the
953 utility written by Kristaps Dzonsons appeared in
958 reference was written by
959 .An Kristaps Dzonsons Aq kristaps@bsd.lv .
961 Do not use this language.