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

cabal run sends bluid info and "Up to date" to stdout, should send to stderr #8329

Closed
alpha-bit opened this issue Jul 27, 2022 · 3 comments
Closed

Comments

@alpha-bit
Copy link

Describe the bug

On cabal run ... 2> /dev/null the build processed is sent to stdout, even when has already built it sends "Up to date" to stdout.

I use this to test a command line program, i need to be able to use the output of the program.

To Reproduce
try cabal run ... 2> /dev/null

Expected behavior
Expected to all output from cabal run to go to stderr.

System information

  • nix-shell @ Debian
  • cabal-install version 3.6.2.0, ghc version 9.0.2
@ffaf1
Copy link
Collaborator

ffaf1 commented Jul 27, 2022

Would cabal run --verbose=0 my-program suit your workflow?

I am not sure sending stuff to stderr is the correct choice.

@ulysses4ever
Copy link
Collaborator

Thanks for the report! It's a dup of #7790, so I suggest we close.

@alpha-bit
Copy link
Author

@ffaf1 ::: Option --verbose 0 just works great, as needed... :)

( O.o ... i should have checked that. )

I am not sure sending stuff to stderr is the correct choice.

I do think everything not-data (for natural piping) should go to stderr.

[ty], Closing as suggested

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

3 participants