-
Notifications
You must be signed in to change notification settings - Fork 843
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
Allow global options both before and after command #519
Comments
I thought it had been this way for a long time / always. (Global opts must On Sunday, July 5, 2015, Michael Snoyman notifications@github.com wrote:
-- Dan Burton |
I recall getting tripped up several times and needing to move |
I'm pretty sure it's been this way since the start, and it is normal behaviour for optparse-applicative. That said, it's really annoying and worth fixing. |
Haven't rebuilt stack for a week, seems that
So if this isn't working on |
If that were true, |
Using the just-released 0.1.2.0, both of the
What doesn't work is putting command-specific option before the subcommand. E.g.,
|
Please, as part of this issue, make sure that |
@k-bx Since |
Right, that part makes sense. |
@manny-fp yes, adding a note that there are more (global) options available would be nice. Would this need a separate issue? |
@k-bx Making a new issue means it is less likely to be missed, so I would encourage it :) |
For me this didn't work ever: ```stack command --global-opt --command-opt`, i.e. stack build --no-terminal --only-snapshot # doesn't work
stack build --only-snapshot --no-terminal # works
stack --no-terminal build --only-snapshot # works That's why e.g. |
@k-bx Was just looking through the optparse-applicative issue tracker and came across this one filed by @chrisdone that's related to your request pcapriotti/optparse-applicative#138. |
Yeah, that one looks like what I was looking for, thanks.
|
stack init now uses the global --resolver option instead of its own implementation of the same. This changes the CLI behavior: you will have to use `stack --resolver lts-4.1 init` instead of `stack init --resolver lts-4.1` Fixes commercialhaskell#1588
I believe this is a regression, since it seemed to work properly before. See #505. Both of the following should work, but currently only the latter does. This may be an issue in optparse-simple:
Assigning to @manny-fp, but pinging @chrisdone who may have a quick answer.
The text was updated successfully, but these errors were encountered: