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

Boolean command-line options are very order-dependent #798

Closed
ianb opened this issue May 29, 2013 · 1 comment
Closed

Boolean command-line options are very order-dependent #798

ianb opened this issue May 29, 2013 · 1 comment

Comments

@ianb
Copy link

ianb commented May 29, 2013

From what I can tell, options are parsed without any knowledge about whether options take arguments or not. That means that for instance:

grunt sometask --bool-option -v

is treated as though it is the same as:

grunt sometask --bool-option=-v

That's pretty confusing, since alone each of these options will work reasonably. It seems at least the parser should see that the following argument starts with a - and treat it as another option, not an argument to the first option.

@shama
Copy link
Member

shama commented May 29, 2013

This is related to an old bug in nopt. We just need to update the dependency and this will be fixed: See #748 Thanks!

@shama shama closed this as completed May 29, 2013
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

No branches or pull requests

2 participants