1 .\" $Id: man.7,v 1.95 2011/01/12 10:43:22 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: January 12 2011 $
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
63 If the first character of a line is a space, that line is printed
64 with a leading newline.
68 whether in a macro or free-form text line, is ignored to the end of
70 A macro line with only a control character and comment escape,
73 Macro lines with only a control character and optionally whitespace are
75 .Ss Special Characters
76 Special characters may occur in both macro and free-form lines.
77 Sequences begin with the escape character
79 followed by either an open-parenthesis
81 for two-character sequences; an open-bracket
83 for n-character sequences (terminated at a close-bracket
85 or a single one-character sequence.
96 Terms may be text-decorated using the
98 escape followed by an indicator: B (bold), I (italic), R (Roman), or P
99 (revert to previous mode):
101 .D1 \efBbold\efR \efIitalic\efP
103 A numerical representation 3, 2, or 1 (bold, italic, and Roman,
104 respectively) may be used instead.
105 A text decoration is only valid, if specified in free-form text, until
106 the next macro invocation; if specified within a macro, it's only valid
107 until the macro closes scope.
108 Note that macros like
110 open and close a font scope with each argument.
114 attribute is forgotten when entering or exiting a macro block.
116 Whitespace consists of the space character.
117 In free-form lines, whitespace is preserved within a line; unescaped
118 trailing spaces are stripped from input (unless in a literal context).
119 Blank free-form lines, which may include spaces, are permitted and
120 rendered as an empty line.
122 In macro lines, whitespace delimits arguments and is discarded.
123 If arguments are quoted, whitespace within the quotes is retained.
129 macro that requires a date.
130 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
140 The syntax for scaled widths is
141 .Sq Li [+-]?[0-9]*.[0-9]*[:unit:]? ,
142 where a decimal must be preceded or proceeded by at least one digit.
143 Negative numbers, while accepted, are truncated to zero.
144 The following scaling units are accepted:
146 .Bl -tag -width Ds -offset indent -compact
159 default vertical span
171 default horizontal span
176 Using anything other than
182 is necessarily non-portable across output media.
184 If a scaling unit is not provided, the numerical value is interpreted
185 under the default rules of
187 for vertical spaces and
193 which, if a unit is not provided, will instead interpret the string as
196 When composing a manual, make sure that sentences end at the end of
198 By doing so, front-ends will be able to apply the proper amount of
199 spacing after the end of sentence (unescaped) period, exclamation mark,
200 or question mark followed by zero or more non-sentence closing
211 document must contain the
213 macro describing the document's section and title.
214 It may occur anywhere in the document, although conventionally it
215 appears as the first macro.
219 at least one macro or text node must appear in the document.
220 Documents are generally structured as follows:
221 .Bd -literal -offset indent
222 \&.TH FOO 1 2009-10-10
224 \efBfoo\efR \e(en a description goes here
226 \&.\e\*q For sections 2 & 3 only.
227 \&.\e\*q Not used in OpenBSD.
229 \efBfoo\efR [\efB\e-options\efR] arguments...
231 The \efBfoo\efR utility processes files...
232 \&.\e\*q .SH IMPLEMENTATION NOTES
233 \&.\e\*q Not used in OpenBSD.
234 \&.\e\*q .SH RETURN VALUES
235 \&.\e\*q For sections 2, 3, & 9 only.
236 \&.\e\*q .SH ENVIRONMENT
237 \&.\e\*q For sections 1, 6, 7, & 8 only.
239 \&.\e\*q .SH EXIT STATUS
240 \&.\e\*q For sections 1, 6, & 8 only.
241 \&.\e\*q .SH EXAMPLES
242 \&.\e\*q .SH DIAGNOSTICS
243 \&.\e\*q For sections 1, 4, 6, 7, & 8 only.
245 \&.\e\*q For sections 2, 3, & 9 only.
246 \&.\e\*q .SH SEE ALSO
247 \&.\e\*q .BR foo ( 1 )
248 \&.\e\*q .SH STANDARDS
253 \&.\e\*q .SH SECURITY CONSIDERATIONS
254 \&.\e\*q Not used in OpenBSD.
259 document are conventionally ordered as they appear above.
260 Sections should be composed as follows:
261 .Bl -ohang -offset indent
263 The name(s) and a short description of the documented material.
264 The syntax for this is generally as follows:
266 .D1 \efBname\efR \e(en description
268 The name of the library containing the documented material, which is
269 assumed to be a function in a section 2 or 3 manual.
270 For functions in the C library, this may be as follows:
272 .D1 Standard C Library (libc, -lc)
274 Documents the utility invocation syntax, function call syntax, or device
277 For the first, utilities (sections 1, 6, and 8), this is
278 generally structured as follows:
280 .D1 \efBname\efR [-\efBab\efR] [-\efBc\efR\efIarg\efR] \efBpath\efR...
282 For the second, function calls (sections 2, 3, 9):
284 .D1 \&.B char *name(char *\efIarg\efR);
286 And for the third, configurations (section 4):
288 .D1 \&.B name* at cardbus ? function ?
290 Manuals not in these sections generally don't need a
293 This expands upon the brief, one-line description in
295 It usually contains a break-down of the options (if documenting a
297 .It Em IMPLEMENTATION NOTES
298 Implementation-specific notes should be kept here.
299 This is useful when implementing standard functions that may have side
300 effects or notable algorithmic implications.
302 This section documents the return values of functions in sections 2, 3, and 9.
304 Documents any usages of environment variables, e.g.,
307 Documents files used.
308 It's helpful to document both the file name and a short description of how
309 the file is used (created, modified, etc.).
311 This section documents the command exit status for
312 section 1, 6, and 8 utilities.
313 Historically, this information was described in
315 a practise that is now discouraged.
318 This often contains snippets of well-formed,
319 well-tested invocations.
320 Make sure that examples work properly!
322 Documents error conditions.
323 This is most useful in section 4 manuals.
324 Historically, this section was used in place of
326 for manuals in sections 1, 6, and 8; however, this practise is
329 Documents error handling in sections 2, 3, and 9.
331 References other manuals with related topics.
332 This section should exist for most manuals.
334 .D1 \&.BR bar \&( 1 \&),
336 Cross-references should conventionally be ordered
337 first by section, then alphabetically.
339 References any standards implemented or used, such as
341 .D1 IEEE Std 1003.2 (\e(lqPOSIX.2\e(rq)
343 If not adhering to any standards, the
345 section should be used.
347 A brief history of the subject, including where support first appeared.
349 Credits to the person or persons who wrote the code and/or documentation.
350 Authors should generally be noted by both name and email address.
352 Common misuses and misunderstandings should be explained
355 Known bugs, limitations, and work-arounds should be described
357 .It Em SECURITY CONSIDERATIONS
358 Documents any security precautions that operators should consider.
361 Macros are one to three characters in length and begin with a
364 at the beginning of the line.
367 macro control character is also accepted.
368 An arbitrary amount of whitespace (spaces or tabs) may sit between the
369 control character and the macro name.
370 Thus, the following are equivalent:
371 .Bd -literal -offset indent
378 macros are classified by scope: line scope or block scope.
379 Line macros are only scoped to the current line (and, in some
380 situations, the subsequent line).
381 Block macros are scoped to the current line and subsequent lines until
382 closed by another block macro.
384 Line macros are generally scoped to the current line, with the body
385 consisting of zero or more arguments.
386 If a macro is scoped to the next line and the line arguments are empty,
387 the next line, which must be text, is used instead.
389 .Bd -literal -offset indent
396 If next-line macros are invoked consecutively, only the last is used.
397 If a next-line macro is followed by a non-next-line macro, an error is
404 The syntax is as follows:
405 .Bd -literal -offset indent
406 \&.YO \(lBbody...\(rB
410 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "ScopeXXXXX" "CompatX"
411 .It Em Macro Ta Em Arguments Ta Em Scope Ta Em Notes
412 .It Sx \&AT Ta <=1 Ta current Ta \&
413 .It Sx \&B Ta n Ta next-line Ta \&
414 .It Sx \&BI Ta n Ta current Ta \&
415 .It Sx \&BR Ta n Ta current Ta \&
416 .It Sx \&DT Ta 0 Ta current Ta \&
417 .It Sx \&I Ta n Ta next-line Ta \&
418 .It Sx \&IB Ta n Ta current Ta \&
419 .It Sx \&IR Ta n Ta current Ta \&
420 .It Sx \&R Ta n Ta next-line Ta \&
421 .It Sx \&RB Ta n Ta current Ta \&
422 .It Sx \&RI Ta n Ta current Ta \&
423 .It Sx \&SB Ta n Ta next-line Ta \&
424 .It Sx \&SM Ta n Ta next-line Ta \&
425 .It Sx \&TH Ta >1, <6 Ta current Ta \&
426 .It Sx \&UC Ta <=1 Ta current Ta \&
427 .It Sx \&br Ta 0 Ta current Ta compat
428 .It Sx \&fi Ta 0 Ta current Ta compat
429 .It Sx \&ft Ta 1 Ta current Ta compat
430 .It Sx \&in Ta 1 Ta current Ta compat
431 .It Sx \&na Ta 0 Ta current Ta compat
432 .It Sx \&nf Ta 0 Ta current Ta compat
433 .It Sx \&sp Ta 1 Ta current Ta compat
438 are included for compatibility with the significant corpus of existing
439 manuals that mix dialects of roff.
440 These macros should not be used for portable
444 Block macros comprise a head and body.
445 As with in-line macros, the head is scoped to the current line and, in
446 one circumstance, the next line (the next-line stipulations as in
450 The syntax is as follows:
451 .Bd -literal -offset indent
452 \&.YO \(lBhead...\(rB
457 The closure of body scope may be to the section, where a macro is closed
460 sub-section, closed by a section or
462 part, closed by a section, sub-section, or
464 or paragraph, closed by a section, sub-section, part,
472 No closure refers to an explicit block closing macro.
474 As a rule, block macros may not be nested; thus, calling a block macro
475 while another block macro scope is open, and the open scope is not
476 implicitly closed, is syntactically incorrect.
478 .Bl -column -compact -offset indent "MacroX" "ArgumentsX" "Head ScopeX" "sub-sectionX" "compatX"
479 .It Em Macro Ta Em Arguments Ta Em Head Scope Ta Em Body Scope Ta Em Notes
480 .It Sx \&HP Ta <2 Ta current Ta paragraph Ta \&
481 .It Sx \&IP Ta <3 Ta current Ta paragraph Ta \&
482 .It Sx \&LP Ta 0 Ta current Ta paragraph Ta \&
483 .It Sx \&P Ta 0 Ta current Ta paragraph Ta \&
484 .It Sx \&PP Ta 0 Ta current Ta paragraph Ta \&
485 .It Sx \&RE Ta 0 Ta current Ta none Ta compat
486 .It Sx \&RS Ta 1 Ta current Ta part Ta compat
487 .It Sx \&SH Ta >0 Ta next-line Ta section Ta \&
488 .It Sx \&SS Ta >0 Ta next-line Ta sub-section Ta \&
489 .It Sx \&TP Ta n Ta next-line Ta paragraph Ta \&
497 If a block macro is next-line scoped, it may only be followed by in-line
498 macros for decorating text.
500 This section is a canonical reference to all macros, arranged
502 For the scoping of individual macros, see
505 Sets the volume for the footer for compatibility with man pages from
508 The optional arguments specify which release it is from.
510 Text is rendered in bold face.
517 Text is rendered alternately in bold face and italic.
519 .Sq .BI this word and that
524 to render in bold face, while
529 Whitespace between arguments is omitted in output.
533 .Dl \&.BI bold italic bold italic
535 The output of this example will be emboldened
539 with spaces stripped between arguments.
549 Text is rendered alternately in bold face and roman (the default font).
550 Whitespace between arguments is omitted in output.
554 for an equivalent example.
565 Included for compatibility.
567 Begin a paragraph whose initial output line is left-justified, but
568 subsequent output lines are indented, with the following syntax:
569 .Bd -filled -offset indent
576 argument must conform to
578 If specified, it's saved for later paragraph left-margins; if unspecified, the
579 saved or default width is used.
589 Text is rendered in italics.
596 Text is rendered alternately in italics and bold face.
597 Whitespace between arguments is omitted in output.
601 for an equivalent example.
611 Begin an indented paragraph with the following syntax:
612 .Bd -filled -offset indent
614 .Op Cm head Op Cm width
619 argument defines the width of the left margin and is defined by
621 It's saved for later paragraph left-margins; if unspecified, the saved or
622 default width is used.
626 argument is used as a leading term, flushed to the left margin.
627 This is useful for bulleted paragraphs and so on.
637 Text is rendered alternately in italics and roman (the default font).
638 Whitespace between arguments is omitted in output.
642 for an equivalent example.
652 Begin an undecorated paragraph.
653 The scope of a paragraph is closed by a subsequent paragraph,
654 sub-section, section, or end of file.
655 The saved paragraph left-margin width is reset to the default.
687 Text is rendered in roman (the default font).
694 Text is rendered alternately in roman (the default font) and bold face.
695 Whitespace between arguments is omitted in output.
699 for an equivalent example.
709 Explicitly close out the scope of a prior
712 Text is rendered alternately in roman (the default font) and italics.
713 Whitespace between arguments is omitted in output.
717 for an equivalent example.
727 Begin a part setting the left margin.
728 The left margin controls the offset, following an initial indentation,
729 to un-indented text such as that of
731 This has the following syntax:
732 .Bd -filled -offset indent
739 argument must conform to
741 If not specified, the saved or default width is used.
743 Text is rendered in small size (one point smaller than the default font)
747 The scope of a section is only closed by another section or the end of
749 The paragraph left-margin width is reset to the default.
751 Text is rendered in small size (one point smaller than the default
755 The scope of a sub-section is closed by a subsequent sub-section,
756 section, or end of file.
757 The paragraph left-margin width is reset to the default.
759 Sets the title of the manual page with the following syntax:
760 .Bd -filled -offset indent
763 .Op Cm date Op Cm source Op Cm volume
766 At least the upper-case document
770 arguments must be provided.
773 argument should be formatted as described in
775 but will be printed verbatim if it is not.
776 If the date is not specified, the current date is used.
779 string specifies the organisation providing the utility.
782 string replaces the default rendered volume, which is dictated by the
787 .Dl \&.TH CVS 5 "1992-02-12" GNU
789 Begin a paragraph where the head, if exceeding the indentation width, is
790 followed by a newline; if not, the body follows on the same line after a
791 buffer to the indentation width.
792 Subsequent output lines are indented.
793 The syntax is as follows:
794 .Bd -filled -offset indent
801 argument must conform to
803 If specified, it's saved for later paragraph left-margins; if
804 unspecified, the saved or default width is used.
814 Sets the volume for the footer for compatibility with man pages from
816 The optional first argument specifies which release it is from.
818 Breaks the current line.
819 Consecutive invocations have no further effect.
824 End literal mode begun by
827 Change the current font mode.
830 for a listing of available font modes.
832 Indent relative to the current indentation:
834 .D1 Pf \. Sx \&in Op Cm width
838 is signed, the new offset is relative.
839 Otherwise, it is absolute.
840 This value is reset upon the next paragraph, section, or sub-section.
842 Don't align to the right margin.
844 Begin literal mode: all subsequent free-form lines have their end of
845 line boundaries preserved.
849 Insert vertical spaces into output with the following syntax:
850 .Bd -filled -offset indent
857 spaces, which must conform to
859 If 0, this is equivalent to the
862 Defaults to 1, if unspecified.
867 This section documents areas of questionable portability between
868 implementations of the
874 In quoted literals, GNU troff allowed pair-wise double-quotes to produce
875 a standalone double-quote in formatted output.
876 It is not known whether this behaviour is exhibited by other formatters.
878 troff suppresses a newline before
880 macro output; in mandoc, it is an alias for the standard
886 .Pq horizontal position ,
888 .Pq vertical position ,
892 .Pq text filling colour ,
894 .Pq zero-length character ,
898 .Pq horizontal position marker ,
900 .Pq text overstrike ,
904 escape sequences are all discarded in mandoc.
908 scaling unit is accepted by mandoc, but rendered as the default unit.
912 macro does not accept negative values in mandoc.
913 In GNU troff, this would result in strange behaviour.
925 language first appeared as a macro package for the roff typesetting
928 It was later rewritten by James Clark as a macro package for groff.
929 The stand-alone implementation that is part of the
931 utility written by Kristaps Dzonsons appeared in
936 reference was written by
937 .An Kristaps Dzonsons Aq kristaps@bsd.lv .
939 Do not use this language.