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

Assume verbosity as silent when invoked in interpreter mode #1472

harendra-kumar opened this Issue Dec 5, 2015 · 3 comments


None yet
3 participants

harendra-kumar commented Dec 5, 2015

Please refer to #1394 for the original discussion.

  • Currently stack prints some output of its own before running the script:

Run from outside a project, using implicit global project config
Using resolver: lts-3.14 from implicit global project's config file: /var/home/harendra/.stack/global-project/stack.yaml

When used as interpreter no other output is desirable other than the script's output itself. In fact this should hold true for any stack exec command. That might interfere with the processing of the script output.

We can fix this by assuming --verbosity silent when invoked as interpreter.


This comment has been minimized.


mgsloan commented Dec 6, 2015

Yup, makes sense to me! Thanks for opening an issue

@mgsloan mgsloan added this to the P2: Should milestone Dec 6, 2015

harendra-kumar added a commit to harendra-kumar/stack that referenced this issue Dec 11, 2015

Delete verbosity option guidance
After the fix for commercialhaskell#1472 the guidance about --verbosity silent is not needed.

This comment has been minimized.


sjakobi commented Feb 6, 2016

This just bit me, when I tried to do some simple timings with a script and see what stack internally does.

I ended up running stack -v runghc script.hs but I'm not entirely sure it does the same thing.

Wouldn't it be enough to have --verbosity silent as a default for the interpreter mode but make it overrideable?


This comment has been minimized.


harendra-kumar commented Jul 7, 2016

I am closing this. Let's keep track of fixing the override issue in #2343.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment