-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Handling option --parse #154
Comments
Parse for what? Because if we make commands friendly, touch know that? |
Closing since OP has had a year to explain what they actual mean |
@thethomaseffect @alejonext sorry I didn't notice the request (plus it came from September 15, not July 20, so it technically wasn't a year) What I meant was that how do you configure commander to handle the flag --parse? For example:
|
There's a couple of issues open related to options sharing the same namespace as commander's internals. We're waiting on getting a pull request updated before merging, please see #35 |
Is it possible to process the --parse flag?
The text was updated successfully, but these errors were encountered: