We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
--cwd Change current directory before executing
I'm happy to make a PR, this shouldn't be too hard to do.
My motivation is running benchmarks in aeson
The text was updated successfully, but these errors were encountered:
I don't have a problem with such an addition, PR definitely welcome, but I'm curious: why isn't using cd an option in this case?
Sorry, something went wrong.
@snoyberg the difference isn't big, but IMHO the first variant is hacky (note ../)
aeson$ (cd benchmarks && STACK_YAML=../stack-bench.yaml stack exec -- aeson-benchmark-typed encodeGeneric/direct/twitter100 +RTS -s)
aeson$ STACK_YAML=stack-bench.yaml stack exec --cwd benchmarks -- aeson-benchmark-typed encodeGeneric/direct/twitter100 +RTS -s
Implement commercialhaskell#3264 adding --cwd to exec
Welcome for any suggestions as to better methods to use/docs to update.
Hey I just implemented this - works fine from the console. I'm happy to make any improvements, but it is pretty straight forward :)
This is run from the stack directory:
# khan at Loki in ~/Dropbox/hask/stack on git:3264-add-cwd-to-exec ● [23:26:34]
→ stack exec -- stack -- exec --cwd dist ls
# khan at Loki in ~/Dropbox/hask/stack on git:3264-add-cwd-to-exec ● [23:26:41]
→ stack exec -- stack -- exec ls
CONTRIBUTING.md LICENSE Setup.hs appveyor.yml dist dot-dir-locals.el mkdocs.yml stack-nightly.yaml stack.yaml
ChangeLog.md README.md TAGS cabal.sandbox.config doc etc src stack.cabal test
Merge pull request #3497 from khanage/3264-add-cwd-to-exec
Implement #3264 adding --cwd to exec
Add ChangeLog entry for #3264
Add ChangeLog entry for commercialhaskell#3264
Why wasn't this flag propagated to stack test command?
No branches or pull requests