Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the ability to generate manpages #7

Merged
merged 5 commits into from
Mar 17, 2022
Merged

Add the ability to generate manpages #7

merged 5 commits into from
Mar 17, 2022

Conversation

peap
Copy link
Owner

@peap peap commented Mar 17, 2022

This partially addresses the request in #5. A new binary, generate-manpage, can be used to create a manpage, which can then be installed by the user wherever manpages go. A new subcommand, install-manpage, suggests where such a file should be placed, but doesn't do it (yet?).

peap added 5 commits July 18, 2021 00:07
Add a config field with initial ideas about where manpages should be
placed on a few operating system types: Linux, macOS, MinGW64 on Windows
(used by git-bash, for instance). Plumb in the new subcommand, but don't
make it do anything yet, other than print out this path. Add this path
and detected OS to the output of `info`.

Also, re-alphabetize the README and other places that list all
subcommands.
This translates the `clap::App` to a `man::Manual` and prints it to
STDOUT. Ideally, `clap` would do this for us (e.g., as described
in https://rust-cli.github.io/book/in-depth/docs.html), but it's
not implemented yet in clap 3 as far as I can tell.
@peap peap merged commit d86d5b6 into master Mar 17, 2022
@peap peap deleted the manpage branch March 17, 2022 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant