Hash :
476e634a
Author :
Thomas de Grivel
Date :
2023-01-21T15:08:36
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326
This is help2man.info, produced by makeinfo version 4.1 from
help2man.texi.
INFO-DIR-SECTION GNU admin
START-INFO-DIR-ENTRY
* help2man: (help2man). Automatic manual page generation.
END-INFO-DIR-ENTRY
This file documents the GNU `help2man' command which produces simple
manual pages from the `--help' and `--version' output of other commands.
Copyright (C) 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Permission is granted to copy and distribute translations of this
manual into another language, under the above conditions for modified
versions, except that this permission notice may be stated in a
translation approved by the Foundation.
File: help2man.info, Node: Top, Next: Overview, Up: (dir)
`help2man'
**********
`help2man' produces simple manual pages from the `--help' and
`--version' output of other commands.
* Menu:
* Overview:: Overview of `help2man'.
* Invoking help2man:: How to run `help2man'.
* Including text:: Including additional text in the output.
* --help recommendations:: Recommended formatting for --help output.
* Makefile usage:: Using `help2man' with `make'.
* Reports:: Reporting bugs or suggestions.
* Availability:: Obtaining `help2man'.
File: help2man.info, Node: Overview, Next: Invoking help2man, Prev: Top, Up: Top
Overview of `help2man'
**********************
`help2man' is a tool for automatically generating simple manual
pages from program output.
Although manual pages are optional for GNU programs other projects,
such as Debian require them (*note Man Pages: (standards)Man Pages.)
This program is intended to provide an easy way for software authors
to include a manual page in their distribution without having to
maintain that document.
Given a program which produces reasonably standard `--help' and
`--version' outputs, `help2man' can re-arrange that output into
something which resembles a manual page.
File: help2man.info, Node: Invoking help2man, Next: Including text, Prev: Overview, Up: Top
How to Run `help2man'
*********************
The format for running the `help2man' program is:
`help2man' [OPTION]... EXECUTABLE
`help2man' supports the following options:
`-n STRING'
`--name=STRING'
Use STRING as the description for the `NAME' paragraph of the
manual page.
By default (for want of anything better) this paragraph contains
`manual page for PROGRAM VERSION'.
This option overrides an include file `[name]' section (*note
Including text::).
`-s SECTION'
`--section SECTION'
Use SECTION as the section for the man page. The default section
is 1.
`-m MANUAL'
`--manual=MANUAL'
Set the name of the manual section to SECTION, used as a centred
heading for the manual page. By default `User Commands' is used
for pages in section 1, `Games' for section 6 and `System
Administration Utilities' for sections 8 and 1M.
`-S SOURCE'
`--source=SOURCE'
The program source is used as a page footer, and often contains
the name of the organisation or a suite of which the program is
part. By default the value is the package name and version.
`-i FILE'
`--include=FILE'
Include material from FILE (*note Including text::).
`-I FILE'
`--opt-include=FILE'
A variant of `--include' for use in Makefile pattern rules which
does not require FILE to exist.
`-o FILE'
`--output=FILE'
Send output to FILE rather than `stdout'.
`-N'
`--no-info'
Suppress inclusion of a `SEE ALSO' paragraph directing the reader
to the Texinfo documentation.
`--help'
`--version'
Show help or version information.
By default `help2man' passes the standard `--help' and `--version'
options to the executable although alternatives may be specified using:
`-h OPTION'
`--help-option=OPTION'
help option string
`-v OPTION'
`--version-option=OPTION'
version option string
File: help2man.info, Node: --help recommendations, Next: Makefile usage, Prev: Including text, Up: Top
`--help' Recommendations
************************
Here are some recommendations for what to include in your `--help'
output. Including these gives `help2man' the best chance at generating
a respectable man page, as well as benefitting users directly.
*Note Command-Line Interfaces: (GNU Coding Standards)Command-Line
Interfaces, and *Note Man Pages: (GNU Coding Standards)Man Pages, for
the official GNU standards relating to `--help' and man pages.
* A synopsis of how to invoke the program. If different usages of
the program have different invocations, then list them all. For
example (edited for brevity):
Usage: cp [OPTION]... SOURCE DEST
or: cp [OPTION]... SOURCE... DIRECTORY
...
Use `argv[0]' for the program name in these synopses, just as it
is, with no directory stripping. This is in contrast to the
canonical (constant) name of the program which is used in
`--version'.
* A very brief explanation of what the program does, including
default and/or typical behavior. For example, here is `cp''s:
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY.
* A list of options, indented to column 2. If the program supports
one-character options, put those first, then the equivalent long
option (if any). If the option takes an argument, include that
too, giving it a meaningful name. Align the descriptions in a
convenient column, if desired. Note that to be correctly
recognised by `help2man' the description must be separated from
the options by at least two spaces and descriptions continued on
subsequent lines must start at the same column.
Here again is an (edited) excerpt from `cp', showing a short
option with an equivalent long option, a long option only, and a
short option only:
-a, --archive same as -dpR
--backup[=CONTROL] make a backup of each ...
-b like --backup but ...
For programs that take many options, it may be desirable to split
the option list into sections such as `Global', `Output control',
or whatever makes sense in the particular case. It is usually
best to alphabetize (by short option name first, then long) within
each section, or the entire list if there are no sections.
* Any useful additional information about program behavior, such as
influential environment variables, further explanation of options,
etc. For example, `cp' discusses `VERSION_CONTROL' and sparse
files.
* A few examples of typical usage, at your discretion. One good
example is usually worth a thousand words of description, so this
is highly recommended.
* In closing, a line stating how to email bug reports. Typically,
MAILING-ADDRESS will be `bug-PROGRAM@gnu.org'; please use this
form for GNU programs whenever possible. It's also good to
mention the home page of the program, other mailing lists, etc.
The `argp' and `popt' programming interfaces let you specify option
descriptions for `--help' in the same structure as the rest of the
option definition; you may wish to consider using these routines for
option parsing instead of `getopt'.
File: help2man.info, Node: Including text, Next: --help recommendations, Prev: Invoking help2man, Up: Top
Including Additional Text in the Output
***************************************
Additional static text may be included in the generated manual page
by using the `--include' and `--opt-include' options (*note Invoking
help2man::).
The format for files included with these option is simple:
[section]
text
/pattern/
text
Blocks of verbatim *roff text are inserted into the output either at
the start of the given `[section]' (case insensitive), or after a
paragraph matching `/pattern/'.
Patterns use the Perl regular expression syntax and may be followed
by the `i', `s' or `m' modifiers (*note perlre(1): (*manpages*)perlre.)
Lines before the first section or pattern which begin with `-' are
processed as options. Anything else is silently ignored and may be
used for comments, RCS keywords and the like.
The section output order is:
NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXAMPLES
_other_
AUTHOR
REPORTING BUGS
COPYRIGHT
SEE ALSO
Any `[name]' or `[synopsis]' sections appearing in the include file
will replace what would have automatically been produced (although you
can still override the former with `--name' if required).
Other sections are prepended to the automatically produced output for
the standard sections given above, or included at _other_ (above) in
the order they were encountered in the include file.
File: help2man.info, Node: Makefile usage, Next: Reports, Prev: --help recommendations, Up: Top
Using `help2man' With `make'
****************************
A suggested use of `help2man' in Makefiles is to have the manual
page depend not on the binary, but on the source file(s) in which the
`--help' and `--version' output are defined.
This usage allows a manual page to be generated by the maintainer and
included in the distribution without requiring the end-user to have
`help2man' installed.
An example rule for the program `prog' could be:
prog.1: $(srcdir)/main.c
-$(HELP2MAN) --output=$@ --name='an example program' ./prog
The value of `HELP2MAN' may be set in `configure.in' using either of:
AM_MISSING_PROG(HELP2MAN, help2man, $missing_dir)
for `automake', or something like:
AC_PATH_PROG(HELP2MAN, help2man, false // No help2man //)
for `autoconf' alone.
File: help2man.info, Node: Reports, Next: Availability, Prev: Makefile usage, Up: Top
Reporting Bugs or Suggestions
*****************************
If you find problems or have suggestions about this program or
manual, please report them to <bug-help2man@gnu.org>.
File: help2man.info, Node: Availability, Prev: Reports, Up: Top
Obtaining `help2man'
********************
The latest version of this distribution is available on-line from:
<ftp://ftp.gnu.org/gnu/help2man/>
Tag Table:
Node: Top1086
Node: Overview1719
Node: Invoking help2man2425
Node: --help recommendations4419
Node: Including text7834
Node: Makefile usage9375
Node: Reports10301
Node: Availability10576
End Tag Table