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.

Sign up for GitHub

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

Jump to bottom

non-boolean-like argument following long bool opt without '=' should be considered as an argument, not an erroneous value #2

Merged
merged 3 commits into from
Feb 3, 2015
Merged

non-boolean-like argument following long bool opt without '=' should be considered as an argument, not an erroneous value #2

merged 3 commits into from
Feb 3, 2015

Commits on Oct 29, 2014

  1. An arg following a bool opt is not a value

    @figdice
    figdice committed Oct 29, 2014
    Configuration menu
    Copy the full SHA
    3a461a0 View commit details
    Browse the repository at this point in the history

Commits on Oct 30, 2014

  1. Used the recommended method of searching val in array. 

    Fixed type comparison to 'boolean'.
    Gabriel Zerbib committed Oct 30, 2014
    Configuration menu
    Copy the full SHA
    8e0d40b View commit details
    Browse the repository at this point in the history

  2. Treat nextArg of boolean long opt like short ones

    @figdice
    figdice committed Oct 30, 2014
    Configuration menu
    Copy the full SHA
    6084e6f View commit details
    Browse the repository at this point in the history