package reason
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=1d09ba24a0594745ab6b38b4d5f81ead8565b73cb69ad46af1c2c26f8d324f00
sha512=542d63c99ab976d011ca39953c022bdd2120177d5905df7ee6ff9623ec4d52c09a323ff7aec95fba5e71611c3850a88172e1c2be94ce68d966b5680ddd436494
doc/reason.cmdliner/Vendored_cmdliner/Manpage/index.html
Module Vendored_cmdliner.ManpageSource
Man page specification.
Man page generation is automatically handled by Cmdliner, consult the details.
The Manpage.block type is used to define a man page's content. It's a good idea to follow the standard manual page structure.
References.
man-pages(7), Conventions for writing Linux man pages.
Man pages
type block = [ | `S of string| `P of string| `Pre of string| `I of string * string| `Noblank| `Blocks of block list
]The type for a block of man page text.
`S sintroduces a new sections, see the standard section names.`P tis a new paragraph with textt.`Pre tis a new preformatted paragraph with textt.`I (l,t)is an indented paragraph with labelland textt.`Noblanksuppresses the blank line introduced between two blocks.`Blocks bssplices the blocksbs.
Except in `Pre, whitespace and newlines are not significant and are all collapsed to a single space. All block strings support the documentation markup language.
escape s escapes s so that it doesn't get interpreted by the documentation markup language.
The type for man page titles. Describes the man page title, section, center_footer, left_footer, center_header.
The type for a man page. A title and the page text as a list of blocks.
The type for man page cross-references.
`Mainrefers to the man page of the program itself.`Cmd cmdrefers to the man page of the program'scmdcommand (which must exist).`Tool binrefers to the command line tool namedbin.`Page (name, sec)refers to the man pagename(sec).
Standard section names and content
The following are standard man page section names, roughly ordered in the order they conventionally appear. See also man man-pages for more elaborations about what sections should contain.
The NAME section. This section is automatically created by Cmdliner for your.
The SYNOPSIS section. By default this section is automatically created by Cmdliner for you, unless it is the first section of your term's man page, in which case it will replace it with yours.
The DESCRIPTION section. This should be a description of what the tool does and provide a little bit of usage and documentation guidance.
The COMMANDS section. By default subcommands get listed here.
The ARGUMENTS section. By default positional arguments get listed here.
The OPTIONS section. By default optional arguments get listed here.
The COMMON OPTIONS section. By default help and version options get listed here. For programs with multiple commands, optional arguments common to all commands can be added here.
The EXIT STATUS section. By default term status exit codes get listed here.
The ENVIRONMENT section. By default environment variables get listed here.
s_environment_intro is the introduction content used by cmdliner when it creates the s_environment section.
The FILES section.
The BUGS section.
The EXAMPLES section.
The AUTHORS section.
The SEE ALSO section.
s_none is a special section named "cmdliner-none" that can be used whenever you do not want something to be listed.
Output
The print function can be useful if the client wants to define other man pages (e.g. to implement a help command).
The type for man page output specification.
`Auto, formats like`Pageror`Plainwhenever theTERMenvironment variable isdumbor unset.`Pager, tries to write to a discovered pager, if that fails uses the`Plainformat.`Plain, formats to plain text.`Groff, formats to groff commands.
val print :
?errs:Format.formatter ->
?subst:(string -> string option) ->
format ->
Format.formatter ->
t ->
unitprint ~errs ~subst fmt ppf page prints page on ppf in the format fmt. subst can be used to perform variable substitution,(defaults to the identity). errs is used to print formatting errors, it defaults to Format.err_formatter.