sphinx-contrib / sphinx-contrib/autoprogram
One manpage per subcommand output
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48
- Forks
- 24
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 1
Description
Is it possible to output multiple manpages/html pages eg for commands with multiple subcommands and a lot of options? I'd like to have the main command in a page and each subcommand in a separate page.
I try as follows but don't get the expected results.
Main command rst file - I try to remove all subcommands in the output my setting maxdepth: 0 but it does not work. Still all subcommands are included in the disco section:
.. autoprogram:: discodos.cmd.cli:ArgParse.parser
:prog: disco
:maxdepth: 0
:groups:
one of the subcommand rst files - works as expected, only the disco searchcommand is shown:
.. autoprogram:: discodos.cmd.cli:ArgParse.parser
:prog: disco
:start_command: search
:maxdepth: 1
:groups
I have some index rst files too and in html output what I am trying to achieve looks quite good already, except the main command issue. These are the index files:
DiscoDOS manual
***************
.. toctree::
:maxdepth: 2
index_commands_reference
Commands reference
******************
.. toctree::
:maxdepth: 1
disco
disco_search
disco_mix
disco_suggest
disco_import
disco_setup
In manpage output I still get one big manpage, containing all subcommands. How can I control that pages should be separated?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the autoprogram entry point discodos.cmd.cli:ArgParse.parser and the disco, disco_search, disco_mix, disco_suggest, disco_import, and disco_setup RST files. Build the documentation in both HTML and manpage formats and compare how :maxdepth: and :start_command: affect the generated pages. Done means the main command and each subcommand are emitted as separate pages in manpage output, matching the existing HTML structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100