xref: /openbsd-src/share/man/man7/man.7 (revision 7f05d21f33214ac08440bb4cdb235c3fa16a6d1e)
1.\"	$OpenBSD: man.7,v 1.16 2011/01/25 00:37:39 schwarze Exp $
2.\"
3.\" Copyright (c) 2009, 2010 Kristaps Dzonsons <kristaps@bsd.lv>
4.\"
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.
8.\"
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.
16.\"
17.Dd $Mdocdate: January 25 2011 $
18.Dt MAN 7
19.Os
20.Sh NAME
21.Nm man
22.Nd man language reference
23.Sh DESCRIPTION
24The
25.Nm man
26language was historically used to format
27.Ux
28manuals.
29This reference document describes its syntax, structure, and usage.
30.Pp
31.Bf -emphasis
32Do not use
33.Nm
34to write your manuals.
35.Ef
36Use the
37.Xr mdoc 7
38language, instead.
39.Pp
40A
41.Nm
42document follows simple rules:  lines beginning with the control
43character
44.Sq \&.
45are parsed for macros.
46Other lines are interpreted within the scope of
47prior macros:
48.Bd -literal -offset indent
49\&.SH Macro lines change control state.
50Other lines are interpreted within the current state.
51.Ed
52.Sh INPUT ENCODING
53.Nm
54documents may contain only graphable 7-bit ASCII characters, the
55space character, and the tab character.
56.Pp
57Blank lines are acceptable; where found, the output will assert a
58vertical space.
59.Pp
60If the first character of a line is a space, that line is printed
61with a leading newline.
62.Ss Comments
63Text following a
64.Sq \e\*q ,
65whether in a macro or free-form text line, is ignored to the end of
66line.
67A macro line with only a control character and comment escape,
68.Sq \&.\e\*q ,
69is also ignored.
70Macro lines with only a control character and optionally whitespace are
71stripped from input.
72.Ss Special Characters
73Special characters may occur in both macro and free-form lines.
74Sequences begin with the escape character
75.Sq \e
76followed by either an open-parenthesis
77.Sq \&(
78for two-character sequences; an open-bracket
79.Sq \&[
80for n-character sequences (terminated at a close-bracket
81.Sq \&] ) ;
82or a single one-character sequence.
83See
84.Xr mandoc_char 7
85for a complete list.
86Examples include
87.Sq \e(em
88.Pq em-dash
89and
90.Sq \ee
91.Pq back-slash .
92.Ss Text Decoration
93Terms may be text-decorated using the
94.Sq \ef
95escape followed by an indicator: B (bold), I (italic), R (Roman), or P
96(revert to previous mode):
97.Pp
98.D1 \efBbold\efR \efIitalic\efP
99.Pp
100A numerical representation 3, 2, or 1 (bold, italic, and Roman,
101respectively) may be used instead.
102A text decoration is only valid, if specified in free-form text, until
103the next macro invocation; if specified within a macro, it's only valid
104until the macro closes scope.
105Note that macros like
106.Sx \&BR
107open and close a font scope with each argument.
108.Pp
109The
110.Sq \ef
111attribute is forgotten when entering or exiting a macro block.
112.Ss Whitespace
113Whitespace consists of the space character.
114In free-form lines, whitespace is preserved within a line; unescaped
115trailing spaces are stripped from input (unless in a literal context).
116Blank free-form lines, which may include spaces, are permitted and
117rendered as an empty line.
118.Pp
119In macro lines, whitespace delimits arguments and is discarded.
120If arguments are quoted, whitespace within the quotes is retained.
121.Ss Dates
122The
123.Sx \&TH
124macro is the only
125.Nm
126macro that requires a date.
127The form for this date is the ISO-8601
128standard
129.Cm YYYY-MM-DD .
130.Ss Scaling Widths
131Many macros support scaled widths for their arguments, such as
132stipulating a two-inch paragraph indentation with the following:
133.Bd -literal -offset indent
134\&.HP 2i
135.Ed
136.Pp
137The syntax for scaled widths is
138.Sq Li [+-]?[0-9]*.[0-9]*[:unit:]? ,
139where a decimal must be preceded or proceeded by at least one digit.
140Negative numbers, while accepted, are truncated to zero.
141The following scaling units are accepted:
142.Pp
143.Bl -tag -width Ds -offset indent -compact
144.It c
145centimetre
146.It i
147inch
148.It P
149pica (~1/6 inch)
150.It p
151point (~1/72 inch)
152.It f
153synonym for
154.Sq u
155.It v
156default vertical span
157.It m
158width of rendered
159.Sq m
160.Pq em
161character
162.It n
163width of rendered
164.Sq n
165.Pq en
166character
167.It u
168default horizontal span
169.It M
170mini-em (~1/100 em)
171.El
172.Pp
173Using anything other than
174.Sq m ,
175.Sq n ,
176.Sq u ,
177or
178.Sq v
179is necessarily non-portable across output media.
180.Pp
181If a scaling unit is not provided, the numerical value is interpreted
182under the default rules of
183.Sq v
184for vertical spaces and
185.Sq u
186for horizontal ones.
187.Em Note :
188this differs from
189.Xr mdoc 7 ,
190which, if a unit is not provided, will instead interpret the string as
191literal text.
192.Ss Sentence Spacing
193When composing a manual, make sure that sentences end at the end of
194a line.
195By doing so, front-ends will be able to apply the proper amount of
196spacing after the end of sentence (unescaped) period, exclamation mark,
197or question mark followed by zero or more non-sentence closing
198delimiters
199.Po
200.Sq \&) ,
201.Sq \&] ,
202.Sq \&' ,
203.Sq \&"
204.Pc .
205.Sh MANUAL STRUCTURE
206Each
207.Nm
208document must contain the
209.Sx \&TH
210macro describing the document's section and title.
211It may occur anywhere in the document, although conventionally it
212appears as the first macro.
213.Pp
214Beyond
215.Sx \&TH ,
216at least one macro or text node must appear in the document.
217Documents are generally structured as follows:
218.Bd -literal -offset indent
219\&.TH FOO 1 2009-10-10
220\&.SH NAME
221\efBfoo\efR \e(en a description goes here
222\&.\e\*q .SH LIBRARY
223\&.\e\*q For sections 2 & 3 only.
224\&.\e\*q Not used in OpenBSD.
225\&.SH SYNOPSIS
226\efBfoo\efR [\efB\e-options\efR] arguments...
227\&.SH DESCRIPTION
228The \efBfoo\efR utility processes files...
229\&.\e\*q .SH IMPLEMENTATION NOTES
230\&.\e\*q Not used in OpenBSD.
231\&.\e\*q .SH RETURN VALUES
232\&.\e\*q For sections 2, 3, & 9 only.
233\&.\e\*q .SH ENVIRONMENT
234\&.\e\*q For sections 1, 6, 7, & 8 only.
235\&.\e\*q .SH FILES
236\&.\e\*q .SH EXIT STATUS
237\&.\e\*q For sections 1, 6, & 8 only.
238\&.\e\*q .SH EXAMPLES
239\&.\e\*q .SH DIAGNOSTICS
240\&.\e\*q For sections 1, 4, 6, 7, & 8 only.
241\&.\e\*q .SH ERRORS
242\&.\e\*q For sections 2, 3, & 9 only.
243\&.\e\*q .SH SEE ALSO
244\&.\e\*q .BR foo ( 1 )
245\&.\e\*q .SH STANDARDS
246\&.\e\*q .SH HISTORY
247\&.\e\*q .SH AUTHORS
248\&.\e\*q .SH CAVEATS
249\&.\e\*q .SH BUGS
250\&.\e\*q .SH SECURITY CONSIDERATIONS
251\&.\e\*q Not used in OpenBSD.
252.Ed
253.Pp
254The sections in a
255.Nm
256document are conventionally ordered as they appear above.
257Sections should be composed as follows:
258.Bl -ohang -offset indent
259.It Em NAME
260The name(s) and a short description of the documented material.
261The syntax for this is generally as follows:
262.Pp
263.D1 \efBname\efR \e(en description
264.It Em LIBRARY
265The name of the library containing the documented material, which is
266assumed to be a function in a section 2 or 3 manual.
267For functions in the C library, this may be as follows:
268.Pp
269.D1 Standard C Library (libc, -lc)
270.It Em SYNOPSIS
271Documents the utility invocation syntax, function call syntax, or device
272configuration.
273.Pp
274For the first, utilities (sections 1, 6, and 8), this is
275generally structured as follows:
276.Pp
277.D1 \efBname\efR [-\efBab\efR] [-\efBc\efR\efIarg\efR] \efBpath\efR...
278.Pp
279For the second, function calls (sections 2, 3, 9):
280.Pp
281.D1 \&.B char *name(char *\efIarg\efR);
282.Pp
283And for the third, configurations (section 4):
284.Pp
285.D1 \&.B name* at cardbus ? function ?
286.Pp
287Manuals not in these sections generally don't need a
288.Em SYNOPSIS .
289.It Em DESCRIPTION
290This expands upon the brief, one-line description in
291.Em NAME .
292It usually contains a break-down of the options (if documenting a
293command).
294.It Em IMPLEMENTATION NOTES
295Implementation-specific notes should be kept here.
296This is useful when implementing standard functions that may have side
297effects or notable algorithmic implications.
298.It Em RETURN VALUES
299This section documents the return values of functions in sections 2, 3, and 9.
300.It Em ENVIRONMENT
301Documents any usages of environment variables, e.g.,
302.Xr environ 7 .
303.It Em FILES
304Documents files used.
305It's helpful to document both the file name and a short description of how
306the file is used (created, modified, etc.).
307.It Em EXIT STATUS
308This section documents the command exit status for
309section 1, 6, and 8 utilities.
310Historically, this information was described in
311.Em DIAGNOSTICS ,
312a practise that is now discouraged.
313.It Em EXAMPLES
314Example usages.
315This often contains snippets of well-formed,
316well-tested invocations.
317Make sure that examples work properly!
318.It Em DIAGNOSTICS
319Documents error conditions.
320This is most useful in section 4 manuals.
321Historically, this section was used in place of
322.Em EXIT STATUS
323for manuals in sections 1, 6, and 8; however, this practise is
324discouraged.
325.It Em ERRORS
326Documents error handling in sections 2, 3, and 9.
327.It Em SEE ALSO
328References other manuals with related topics.
329This section should exist for most manuals.
330.Pp
331.D1 \&.BR bar \&( 1 \&),
332.Pp
333Cross-references should conventionally be ordered
334first by section, then alphabetically.
335.It Em STANDARDS
336References any standards implemented or used, such as
337.Pp
338.D1 IEEE Std 1003.2 (\e(lqPOSIX.2\e(rq)
339.Pp
340If not adhering to any standards, the
341.Em HISTORY
342section should be used.
343.It Em HISTORY
344A brief history of the subject, including where support first appeared.
345.It Em AUTHORS
346Credits to the person or persons who wrote the code and/or documentation.
347Authors should generally be noted by both name and email address.
348.It Em CAVEATS
349Common misuses and misunderstandings should be explained
350in this section.
351.It Em BUGS
352Known bugs, limitations, and work-arounds should be described
353in this section.
354.It Em SECURITY CONSIDERATIONS
355Documents any security precautions that operators should consider.
356.El
357.Sh MACRO SYNTAX
358Macros are one to three characters in length and begin with a
359control character,
360.Sq \&. ,
361at the beginning of the line.
362The
363.Sq \(aq
364macro control character is also accepted.
365An arbitrary amount of whitespace (spaces or tabs) may sit between the
366control character and the macro name.
367Thus, the following are equivalent:
368.Bd -literal -offset indent
369\&.PP
370\&.\ \ \ PP
371.Ed
372.Pp
373To include space characters in macro arguments, arguments may be quoted;
374see the
375.Sq MACRO SYNTAX
376section in the
377.Xr roff 7
378manual for details.
379.Pp
380The
381.Nm
382macros are classified by scope: line scope or block scope.
383Line macros are only scoped to the current line (and, in some
384situations, the subsequent line).
385Block macros are scoped to the current line and subsequent lines until
386closed by another block macro.
387.Ss Line Macros
388Line macros are generally scoped to the current line, with the body
389consisting of zero or more arguments.
390If a macro is scoped to the next line and the line arguments are empty,
391the next line, which must be text, is used instead.
392Thus:
393.Bd -literal -offset indent
394\&.I
395foo
396.Ed
397.Pp
398is equivalent to
399.Sq \&.I foo .
400If next-line macros are invoked consecutively, only the last is used.
401If a next-line macro is followed by a non-next-line macro, an error is
402raised, except for
403.Sx \&br ,
404.Sx \&sp ,
405and
406.Sx \&na .
407.Pp
408The syntax is as follows:
409.Bd -literal -offset indent
410\&.YO \(lBbody...\(rB
411\(lBbody...\(rB
412.Ed
413.Pp
414.Bl -column -compact -offset indent "MacroX" "ArgumentsX" "ScopeXXXXX" "CompatX"
415.It Em Macro Ta Em Arguments Ta Em Scope     Ta Em Notes
416.It Sx \&AT  Ta    <=1       Ta    current   Ta    \&
417.It Sx \&B   Ta    n         Ta    next-line Ta    \&
418.It Sx \&BI  Ta    n         Ta    current   Ta    \&
419.It Sx \&BR  Ta    n         Ta    current   Ta    \&
420.It Sx \&DT  Ta    0         Ta    current   Ta    \&
421.It Sx \&I   Ta    n         Ta    next-line Ta    \&
422.It Sx \&IB  Ta    n         Ta    current   Ta    \&
423.It Sx \&IR  Ta    n         Ta    current   Ta    \&
424.It Sx \&R   Ta    n         Ta    next-line Ta    \&
425.It Sx \&RB  Ta    n         Ta    current   Ta    \&
426.It Sx \&RI  Ta    n         Ta    current   Ta    \&
427.It Sx \&SB  Ta    n         Ta    next-line Ta    \&
428.It Sx \&SM  Ta    n         Ta    next-line Ta    \&
429.It Sx \&TH  Ta    >1, <6    Ta    current   Ta    \&
430.It Sx \&UC  Ta    <=1       Ta    current   Ta    \&
431.It Sx \&br  Ta    0         Ta    current   Ta    compat
432.It Sx \&fi  Ta    0         Ta    current   Ta    compat
433.It Sx \&in  Ta    1         Ta    current   Ta    compat
434.It Sx \&na  Ta    0         Ta    current   Ta    compat
435.It Sx \&nf  Ta    0         Ta    current   Ta    compat
436.It Sx \&sp  Ta    1         Ta    current   Ta    compat
437.El
438.Pp
439Macros marked as
440.Qq compat
441are included for compatibility with the significant corpus of existing
442manuals that mix dialects of roff.
443These macros should not be used for portable
444.Nm
445manuals.
446.Ss Block Macros
447Block macros comprise a head and body.
448As with in-line macros, the head is scoped to the current line and, in
449one circumstance, the next line (the next-line stipulations as in
450.Sx Line Macros
451apply here as well).
452.Pp
453The syntax is as follows:
454.Bd -literal -offset indent
455\&.YO \(lBhead...\(rB
456\(lBhead...\(rB
457\(lBbody...\(rB
458.Ed
459.Pp
460The closure of body scope may be to the section, where a macro is closed
461by
462.Sx \&SH ;
463sub-section, closed by a section or
464.Sx \&SS ;
465part, closed by a section, sub-section, or
466.Sx \&RE ;
467or paragraph, closed by a section, sub-section, part,
468.Sx \&HP ,
469.Sx \&IP ,
470.Sx \&LP ,
471.Sx \&P ,
472.Sx \&PP ,
473or
474.Sx \&TP .
475No closure refers to an explicit block closing macro.
476.Pp
477As a rule, block macros may not be nested; thus, calling a block macro
478while another block macro scope is open, and the open scope is not
479implicitly closed, is syntactically incorrect.
480.Pp
481.Bl -column -compact -offset indent "MacroX" "ArgumentsX" "Head ScopeX" "sub-sectionX" "compatX"
482.It Em Macro Ta Em Arguments Ta Em Head Scope Ta Em Body Scope  Ta Em Notes
483.It Sx \&HP  Ta    <2        Ta    current    Ta    paragraph   Ta    \&
484.It Sx \&IP  Ta    <3        Ta    current    Ta    paragraph   Ta    \&
485.It Sx \&LP  Ta    0         Ta    current    Ta    paragraph   Ta    \&
486.It Sx \&P   Ta    0         Ta    current    Ta    paragraph   Ta    \&
487.It Sx \&PP  Ta    0         Ta    current    Ta    paragraph   Ta    \&
488.It Sx \&RE  Ta    0         Ta    current    Ta    none        Ta    compat
489.It Sx \&RS  Ta    1         Ta    current    Ta    part        Ta    compat
490.It Sx \&SH  Ta    >0        Ta    next-line  Ta    section     Ta    \&
491.It Sx \&SS  Ta    >0        Ta    next-line  Ta    sub-section Ta    \&
492.It Sx \&TP  Ta    n         Ta    next-line  Ta    paragraph   Ta    \&
493.El
494.Pp
495Macros marked
496.Qq compat
497are as mentioned in
498.Sx Line Macros .
499.Pp
500If a block macro is next-line scoped, it may only be followed by in-line
501macros for decorating text.
502.Sh REFERENCE
503This section is a canonical reference to all macros, arranged
504alphabetically.
505For the scoping of individual macros, see
506.Sx MACRO SYNTAX .
507.Ss \&AT
508Sets the volume for the footer for compatibility with man pages from
509.Tn AT&T UNIX
510releases.
511The optional arguments specify which release it is from.
512.Ss \&B
513Text is rendered in bold face.
514.Pp
515See also
516.Sx \&I
517and
518.Sx \&R .
519.Ss \&BI
520Text is rendered alternately in bold face and italic.
521Thus,
522.Sq .BI this word and that
523causes
524.Sq this
525and
526.Sq and
527to render in bold face, while
528.Sq word
529and
530.Sq that
531render in italics.
532Whitespace between arguments is omitted in output.
533.Pp
534Examples:
535.Pp
536.Dl \&.BI bold italic bold italic
537.Pp
538The output of this example will be emboldened
539.Dq bold
540and italicised
541.Dq italic ,
542with spaces stripped between arguments.
543.Pp
544See also
545.Sx \&IB ,
546.Sx \&BR ,
547.Sx \&RB ,
548.Sx \&RI ,
549and
550.Sx \&IR .
551.Ss \&BR
552Text is rendered alternately in bold face and roman (the default font).
553Whitespace between arguments is omitted in output.
554.Pp
555See
556.Sx \&BI
557for an equivalent example.
558.Pp
559See also
560.Sx \&BI ,
561.Sx \&IB ,
562.Sx \&RB ,
563.Sx \&RI ,
564and
565.Sx \&IR .
566.Ss \&DT
567Has no effect.
568Included for compatibility.
569.Ss \&HP
570Begin a paragraph whose initial output line is left-justified, but
571subsequent output lines are indented, with the following syntax:
572.Bd -filled -offset indent
573.Pf \. Sx \&HP
574.Op Cm width
575.Ed
576.Pp
577The
578.Cm width
579argument must conform to
580.Sx Scaling Widths .
581If specified, it's saved for later paragraph left-margins; if unspecified, the
582saved or default width is used.
583.Pp
584See also
585.Sx \&IP ,
586.Sx \&LP ,
587.Sx \&P ,
588.Sx \&PP ,
589and
590.Sx \&TP .
591.Ss \&I
592Text is rendered in italics.
593.Pp
594See also
595.Sx \&B
596and
597.Sx \&R .
598.Ss \&IB
599Text is rendered alternately in italics and bold face.
600Whitespace between arguments is omitted in output.
601.Pp
602See
603.Sx \&BI
604for an equivalent example.
605.Pp
606See also
607.Sx \&BI ,
608.Sx \&BR ,
609.Sx \&RB ,
610.Sx \&RI ,
611and
612.Sx \&IR .
613.Ss \&IP
614Begin an indented paragraph with the following syntax:
615.Bd -filled -offset indent
616.Pf \. Sx \&IP
617.Op Cm head Op Cm width
618.Ed
619.Pp
620The
621.Cm width
622argument defines the width of the left margin and is defined by
623.Sx Scaling Widths .
624It's saved for later paragraph left-margins; if unspecified, the saved or
625default width is used.
626.Pp
627The
628.Cm head
629argument is used as a leading term, flushed to the left margin.
630This is useful for bulleted paragraphs and so on.
631.Pp
632See also
633.Sx \&HP ,
634.Sx \&LP ,
635.Sx \&P ,
636.Sx \&PP ,
637and
638.Sx \&TP .
639.Ss \&IR
640Text is rendered alternately in italics and roman (the default font).
641Whitespace between arguments is omitted in output.
642.Pp
643See
644.Sx \&BI
645for an equivalent example.
646.Pp
647See also
648.Sx \&BI ,
649.Sx \&IB ,
650.Sx \&BR ,
651.Sx \&RB ,
652and
653.Sx \&RI .
654.Ss \&LP
655Begin an undecorated paragraph.
656The scope of a paragraph is closed by a subsequent paragraph,
657sub-section, section, or end of file.
658The saved paragraph left-margin width is reset to the default.
659.Pp
660See also
661.Sx \&HP ,
662.Sx \&IP ,
663.Sx \&P ,
664.Sx \&PP ,
665and
666.Sx \&TP .
667.Ss \&P
668Synonym for
669.Sx \&LP .
670.Pp
671See also
672.Sx \&HP ,
673.Sx \&IP ,
674.Sx \&LP ,
675.Sx \&PP ,
676and
677.Sx \&TP .
678.Ss \&PP
679Synonym for
680.Sx \&LP .
681.Pp
682See also
683.Sx \&HP ,
684.Sx \&IP ,
685.Sx \&LP ,
686.Sx \&P ,
687and
688.Sx \&TP .
689.Ss \&R
690Text is rendered in roman (the default font).
691.Pp
692See also
693.Sx \&I
694and
695.Sx \&B .
696.Ss \&RB
697Text is rendered alternately in roman (the default font) and bold face.
698Whitespace between arguments is omitted in output.
699.Pp
700See
701.Sx \&BI
702for an equivalent example.
703.Pp
704See also
705.Sx \&BI ,
706.Sx \&IB ,
707.Sx \&BR ,
708.Sx \&RI ,
709and
710.Sx \&IR .
711.Ss \&RE
712Explicitly close out the scope of a prior
713.Sx \&RS .
714.Ss \&RI
715Text is rendered alternately in roman (the default font) and italics.
716Whitespace between arguments is omitted in output.
717.Pp
718See
719.Sx \&BI
720for an equivalent example.
721.Pp
722See also
723.Sx \&BI ,
724.Sx \&IB ,
725.Sx \&BR ,
726.Sx \&RB ,
727and
728.Sx \&IR .
729.Ss \&RS
730Begin a part setting the left margin.
731The left margin controls the offset, following an initial indentation,
732to un-indented text such as that of
733.Sx \&PP .
734This has the following syntax:
735.Bd -filled -offset indent
736.Pf \. Sx \&Rs
737.Op Cm width
738.Ed
739.Pp
740The
741.Cm width
742argument must conform to
743.Sx Scaling Widths .
744If not specified, the saved or default width is used.
745.Ss \&SB
746Text is rendered in small size (one point smaller than the default font)
747bold face.
748.Ss \&SH
749Begin a section.
750The scope of a section is only closed by another section or the end of
751file.
752The paragraph left-margin width is reset to the default.
753.Ss \&SM
754Text is rendered in small size (one point smaller than the default
755font).
756.Ss \&SS
757Begin a sub-section.
758The scope of a sub-section is closed by a subsequent sub-section,
759section, or end of file.
760The paragraph left-margin width is reset to the default.
761.Ss \&TH
762Sets the title of the manual page with the following syntax:
763.Bd -filled -offset indent
764.Pf \. Sx \&TH
765.Cm title section
766.Op Cm date Op Cm source Op Cm volume
767.Ed
768.Pp
769At least the upper-case document
770.Cm title
771and the manual
772.Cm section
773arguments must be provided.
774The
775.Cm date
776argument should be formatted as described in
777.Sx Dates ,
778but will be printed verbatim if it is not.
779If the date is not specified, the current date is used.
780The
781.Cm source
782string specifies the organisation providing the utility.
783The
784.Cm volume
785string replaces the default rendered volume, which is dictated by the
786manual section.
787.Pp
788Examples:
789.Pp
790.Dl \&.TH CVS 5 "1992-02-12" GNU
791.Ss \&TP
792Begin a paragraph where the head, if exceeding the indentation width, is
793followed by a newline; if not, the body follows on the same line after a
794buffer to the indentation width.
795Subsequent output lines are indented.
796The syntax is as follows:
797.Bd -filled -offset indent
798.Pf \. Sx \&TP
799.Op Cm width
800.Ed
801.Pp
802The
803.Cm width
804argument must conform to
805.Sx Scaling Widths .
806If specified, it's saved for later paragraph left-margins; if
807unspecified, the saved or default width is used.
808.Pp
809See also
810.Sx \&HP ,
811.Sx \&IP ,
812.Sx \&LP ,
813.Sx \&P ,
814and
815.Sx \&PP .
816.Ss \&UC
817Sets the volume for the footer for compatibility with man pages from
818BSD releases.
819The optional first argument specifies which release it is from.
820.Ss \&br
821Breaks the current line.
822Consecutive invocations have no further effect.
823.Pp
824See also
825.Sx \&sp .
826.Ss \&fi
827End literal mode begun by
828.Sx \&nf .
829.Ss \&in
830Indent relative to the current indentation:
831.Pp
832.D1 Pf \. Sx \&in Op Cm width
833.Pp
834If
835.Cm width
836is signed, the new offset is relative.
837Otherwise, it is absolute.
838This value is reset upon the next paragraph, section, or sub-section.
839.Ss \&na
840Don't align to the right margin.
841.Ss \&nf
842Begin literal mode: all subsequent free-form lines have their end of
843line boundaries preserved.
844May be ended by
845.Sx \&fi .
846.Ss \&sp
847Insert vertical spaces into output with the following syntax:
848.Bd -filled -offset indent
849.Pf \. Sx \&sp
850.Op Cm height
851.Ed
852.Pp
853Insert
854.Cm height
855spaces, which must conform to
856.Sx Scaling Widths .
857If 0, this is equivalent to the
858.Sx \&br
859macro.
860Defaults to 1, if unspecified.
861.Pp
862See also
863.Sx \&br .
864.Sh COMPATIBILITY
865This section documents areas of questionable portability between
866implementations of the
867.Nm
868language.
869.Pp
870.Bl -dash -compact
871.It
872In quoted literals, GNU troff allowed pair-wise double-quotes to produce
873a standalone double-quote in formatted output.
874It is not known whether this behaviour is exhibited by other formatters.
875.It
876troff suppresses a newline before
877.Sq \(aq
878macro output; in mandoc, it is an alias for the standard
879.Sq \&.
880control character.
881.It
882The
883.Sq \eh
884.Pq horizontal position ,
885.Sq \ev
886.Pq vertical position ,
887.Sq \em
888.Pq text colour ,
889.Sq \eM
890.Pq text filling colour ,
891.Sq \ez
892.Pq zero-length character ,
893.Sq \ew
894.Pq string length ,
895.Sq \ek
896.Pq horizontal position marker ,
897.Sq \eo
898.Pq text overstrike ,
899and
900.Sq \es
901.Pq text size
902escape sequences are all discarded in mandoc.
903.It
904The
905.Sq \ef
906scaling unit is accepted by mandoc, but rendered as the default unit.
907.It
908The
909.Sx \&sp
910macro does not accept negative values in mandoc.
911In GNU troff, this would result in strange behaviour.
912.El
913.Sh SEE ALSO
914.Xr man 1 ,
915.Xr mandoc 1 ,
916.Xr mandoc_char 7 ,
917.Xr mdoc 7 ,
918.Xr roff 7 ,
919.Xr tbl 7
920.Sh HISTORY
921The
922.Nm
923language first appeared as a macro package for the roff typesetting
924system in
925.At v7 .
926It was later rewritten by James Clark as a macro package for groff.
927The stand-alone implementation that is part of the
928.Xr mandoc 1
929utility written by Kristaps Dzonsons appeared in
930.Ox 4.6 .
931.Sh AUTHORS
932This
933.Nm
934reference was written by
935.An Kristaps Dzonsons Aq kristaps@bsd.lv .
936.Sh CAVEATS
937Do not use this language.
938Use
939.Xr mdoc 7 ,
940instead.
941