From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 121211] New: Please provide conventions for documenting subcommands in man-pages(7)
Date: Thu, 30 Jun 2016 09:34:51 +0000 [thread overview]
Message-ID: <bug-121211-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=121211
Bug ID: 121211
Summary: Please provide conventions for documenting subcommands
in man-pages(7)
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P1
Component: man-pages
Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
Reporter: josh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Regression: No
Many programs now provide subcommands, such as git, systemctl, git-remote,
git-hub, and apt. These programs follow various different inconsistent
conventions for documenting these subcommands in their manpages. I'm about to
write such a program with subcommands myself. I'd love to see some standard
conventions documented in man-pages(7).
Note that some programs will want to document all their subcommands in separate
manpages, and others will want a single all-encompassing manpage. I don't
think man-pages(7) should mandate one or the other approach there, just
establish standards that work either way.
In particular:
- Should the SYNOPSIS section document the usage of every subcommand (see
git-remote for an example), or use a placeholders for subcommands and their
options (see systemctl, git, or git-hub for examples)?
- If the SYNOPSIS just uses placeholders, what placeholder should it use for
subcommands? "<command>" or "<subcommand>" or "<cmd>" or "<subcmd>"? (Or
similar with square brackets if optional.)
- What section should subcommands appear in? I've seen both "COMMANDS" and
"SUBCOMMANDS".
- Within that section, what formatting should subcommands use for their name,
usage, description, and options?
- If programs don't ship separate manual pages for each subcommand, should they
ship symlinks for each subcommand to the main manpage?
- How does this work with programs that have multiple levels of subcommand?
(For instance, consider git-remote, which itself has subcommands. Or consider
a third-party git extension, like git-hub, which itself has subcommands.)
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-06-30 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 9:34 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
[not found] ` <bug-121211-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2016-07-07 11:23 ` [Bug 121211] Please provide conventions for documenting subcommands in man-pages(7) bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2016-07-07 17:53 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2016-07-07 18:25 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2016-07-07 18:25 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2016-07-07 18:26 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-121211-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.