-
Notifications
You must be signed in to change notification settings - Fork 74
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
Option parsing error (incomplete option name) #6
Comments
From @d-ash on February 14, 2015 8:55 It seems that the problem is in OptionParser, and it's an old issue. |
Do you have a link to the issue in OptionParser? I would like to understand why it hasn't been fixed there. |
From @d-ash on February 17, 2015 8:26 https://www.ruby-forum.com/topic/143551 |
From @d-ash on February 14, 2015 8:40
Passing only a beginning of a name triggers the option to be set.
For example, if --vagrant option is declared, passing --v or --va... to the script, works as if the full name has been passed.
However, global options work correctly (--v is not equivalent to --vagrant)
Copied from original issue: tj/commander#93
The text was updated successfully, but these errors were encountered: