-
Notifications
You must be signed in to change notification settings - Fork 701
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
new-run doesn't suppress its own stdout when being invoked as part of a pipe #5595
Comments
@hasufell, have you tried
|
Yes, didn't change anything Edit: oh wait, I did I still think this should be automatic. A program can detect whether it's being invoked as part of a "pipe". Most command line programs do that (e.g. git). |
Honestly, I think that some of that information should be going to stderr instead. |
Related: #4789. |
Should this be closed as superseded by #7790? |
Invoking
cabal new-run target -- something > data
is kinda broken, because I get cabal information messages at the front.The text was updated successfully, but these errors were encountered: