-
Notifications
You must be signed in to change notification settings - Fork 842
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
Comments
Yup, makes sense to me! Thanks for opening an issue |
After the fix for commercialhaskell#1472 the guidance about --verbosity silent is not needed.
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 Wouldn't it be enough to have |
I am closing this. Let's keep track of fixing the override issue in #2343. |
Please refer to #1394 for the original discussion.
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.The text was updated successfully, but these errors were encountered: