-
Notifications
You must be signed in to change notification settings - Fork 125
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 man page for the command-line utility #526
Comments
Probably should be done concurrently w/ #472. |
oxipng --help > oxipng.txt |
Given so many recent updates (most of which haven't merged, much less released), I'm not aware whether even the command-line help is current. |
Even like this? Sorry. |
I vaguely remember a discussion someplace in these Issues re: how out-of-date the |
@sorairolake Not saying there shouldn't be a man page, but was there something in particular you were wanting to understand that wasn't explained sufficiently in |
@andrews05 I also think the usage in |
One easy thing we could do is append the help output to the Read Me (in some sort of automated fashion). This would at least make it easily accessible online. |
Thanks @musicinmybrain, see #596 where I’m using that 🙂 |
This PR adds a build script to generate a man page using clap_mangen, as per this example: https://github.com/sondr3/clap-man-example/blob/main/build.rs I'm not sure what to actually do with the man file from here, I guess it's up to the packaging process to do something with it? See #69 (comment) Note I couldn't see a way to include the `DISPLAY` chunk names from the constant as we did before. They're now just hardcoded into the help and will require manually updating if the list changes. Closes #526 --------- Co-authored-by: Alejandro González <[email protected]>
I think this is useful for understanding the detailed usage of the command-line utility.
The text was updated successfully, but these errors were encountered: