Skip to content
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

Closed
hasufell opened this issue Sep 27, 2018 · 5 comments
Closed

Comments

@hasufell
Copy link
Member

Invoking cabal new-run target -- something > data is kinda broken, because I get cabal information messages at the front.

@phadej
Copy link
Collaborator

phadej commented Sep 27, 2018

@hasufell, have you tried

cabal new-run -v0 target -- something > data

@hasufell
Copy link
Member Author

hasufell commented Sep 27, 2018

Yes, didn't change anything

Edit: oh wait, I did -v 0 and not -v0 (the syntax btw is cabal new-run target -v0 -- something > data)

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).

@typedrat
Copy link
Collaborator

typedrat commented Oct 9, 2018

Honestly, I think that some of that information should be going to stderr instead.

@23Skidoo
Copy link
Member

Related: #4789.

@ulysses4ever
Copy link
Collaborator

Should this be closed as superseded by #7790?

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

No branches or pull requests

6 participants