-
Notifications
You must be signed in to change notification settings - Fork 30
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
Show subcommands in help output #18
Conversation
I think it might be a bit verbose. If I want to see what options a subcommand has I can run A list of subcommands followed by description would also be a way to do this. |
Not at the moment, which is why I asked.
This sounds sane. :) |
Ah, yes. I'd love to be able to scope --help to a subcommand if possible. |
Aren't we reinventing the wheel here? Can't we just make it look like it was before mercenary? |
@svnpenn This entire program is reinventing the wheel. Just better. More circular, more perfect. Take a look at the travis output for examples. |
I dont know how to do that. |
@parkr I dig it. However I'd prefer left alignment of subcommands and appropriate padding for descriptions, much like the |
@imathis New screenshot in the main description above. Thinking we should center options around the
Check this out: https://travis-ci.org/jekyll/mercenary/jobs/19274463 |
@parkr Yeah, I'd agree with left justifying options and padding them to center on the |
Jekyll subcommands are for example |
It doesn't contain the Jekyll output – I meant that you can see example output for the commands in the examples. |
--help
and--version
to show their respective subcommandsMercenary::Presenter
Fixes #15.