1 ; This is the scdoc(5) manpage, used to test scdoc-mode.
8 scdoc - document format for writing manual pages
12 Input files must use the UTF-8 encoding.
16 Each scdoc file must begin with the following preamble:
18 *name*(_section_) ["left\_footer" ["center\_header"]]
20 *name* is the name of the man page you are writing, and _section_ is the section
21 you're writing for (see *man*(1) for information on manual sections).
23 _left\_footer_ and _center\_header_ are optional arguments which set the text
24 positioned at those locations in the generated man page, and *must* be
25 surrounded with double quotes.
29 Each section of your man page should begin with something similar to the
34 Subsection headers are also understood - use two hashes. Each header must have
35 an empty line on either side.
39 Begin a new paragraph with an empty line.
43 Insert a line break by ending a line with \+\+.
50 Text can be made *bold* or _underlined_ with asterisks and underscores: \*bold\*
51 or \_underlined\_. Underscores in the_middle_of_words will be disregarded.
55 You may indent lines with tab characters (*\\t*) to indent them by 4 spaces in
56 the output. Indented lines may not contain headers.
58 The result looks something like this.
60 You may use multiple lines and most _formatting_.
62 Deindent to return to normal, or indent again to increase your indentation
67 You may start bulleted lists with dashes (-), like so:
77 The result looks like this:
85 You may also extend long entries onto another line by giving it the same indent
86 level, plus two spaces. They will be rendered as a single list entry.
89 - Item 1 is pretty long so let's
90 break it up onto two lines
92 - But its children can go on
96 - Item 1 is pretty long so let's
97 break it up onto two lines
99 - But its children can go on
104 Numbered lists are similar to normal lists, but begin with periods (.) instead
105 of dashes (-), like so:
121 To begin a table, add an empty line followed by any number of rows.
123 Each line of a table should start with | or : to start a new row or column
124 respectively (or space to continue the previous cell on multiple lines),
125 followed by [ or - or ] to align the contents to the left, center, or right,
126 followed by a space and the contents of that cell. You may use a space instead
127 of an alignment specifier to inherit the alignment of the same column in the
130 The first character of the first row is not limited to | and has special
131 meaning. [ will produce a table with borders around each cell. | will produce a
132 table with no borders. ] will produce a table with one border around the whole
135 To conclude your table, add an empty line after the last row.
161 You may also cause columns to expand to fill the available space with < (left
162 align), = (center align), and > (right align), like so:
178 You may turn off scdoc formatting and output literal text with escape codes and
179 literal blocks. Inserting a \\ into your source will cause the subsequent symbol
180 to be treated as a literal and copied directly to the output. You may also make
181 blocks of literal syntax like so:
185 _This formatting_ will *not* be interpreted by scdoc.
189 These blocks will be indented one level. Note that literal text is shown
190 literally in the man viewer - that is, it's not a means for inserting your own
191 roff macros into the output. Note that \\ is still interpreted within literal
192 blocks, which for example can be useful to output \``` inside of a literal
197 Lines beginning with ; and a space are ignored.
205 By convention, all scdoc documents should be hard wrapped at 80 columns.
213 Maintained by Drew DeVault <sir@cmpwn.com>. Up-to-date sources can be found at
214 https://git.sr.ht/~sircmpwn/scdoc and bugs/patches can be submitted by email to
215 ~sircmpwn/public-inbox@lists.sr.ht.