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