We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
cabal run ... 2> /dev/null
"Up to date"
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.
cabal run
System information
cabal-install version 3.6.2.0
ghc version 9.0.2
The text was updated successfully, but these errors were encountered:
Would cabal run --verbose=0 my-program suit your workflow?
cabal run --verbose=0 my-program
I am not sure sending stuff to stderr is the correct choice.
stderr
Sorry, something went wrong.
Thanks for the report! It's a dup of #7790, so I suggest we close.
@ffaf1 ::: Option --verbose 0 just works great, as needed... :)
--verbose 0
( O.o ... i should have checked that. )
I do think everything not-data (for natural piping) should go to stderr.
[ty], Closing as suggested
No branches or pull requests
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
cabal-install version 3.6.2.0
,ghc version 9.0.2
The text was updated successfully, but these errors were encountered: