Open mpickering opened 5 years ago
I don't think --no-warnings
will be enough. Even besides that, the Haddock codebase still has a bunch of unguarded putStrLn
's for emitting various messages.
Once all that fixed, I think it should be enough to make sure that -v0
in Cabal implies -v0
in Haddock.
@harpocrates Is there a corresponding upstream ticket?
Nope, but there probably should be. There’s some nice beginner-friendly refactor work there to do.
On May 28, 2019, at 3:04 PM, Mikhail Glushenkov notifications@github.com wrote:
@harpocrates https://github.com/harpocrates Is there a corresponding upstream ticket?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/haskell/cabal/issues/5991?email_source=notifications&email_token=ACSEOAKKSOM63JVL3EXVO3DPXWT5LA5CNFSM4HEJLVF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWNSMYQ#issuecomment-496707170, or mute the thread https://github.com/notifications/unsubscribe-auth/ACSEOAMPF5GNGBBJ2YYGHKDPXWT5LANCNFSM4HEJLVFQ.
-v0
should never output anything to stdout. cabal-install should be silent in this mode of operation.If you enable
documentation: true
in a cabal file then a lot of junk from haddock is output.Perhaps passing
--no-warnings
to haddock is sufficient.