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

--verbosity info is too terse compared to --verbosity debug #5323

Closed
juhp opened this issue Jun 19, 2020 · 3 comments
Closed

--verbosity info is too terse compared to --verbosity debug #5323

juhp opened this issue Jun 19, 2020 · 3 comments

Comments

@juhp
Copy link
Contributor

juhp commented Jun 19, 2020

General summary/comments

I would like to have --verbose be an alias for --verbosity info with some of the more informative output from --verbosity debug promoted to info.

eg I don't think stack --verbose should output all of RawSnapshotLayer: for most general stack users it is not useful and it makes for example stack -v install output too heavy.

Steps to reproduce

For example:

  1. run stack -v install

Expected

details like resolver snapshot paths and compiler chosen, etc

Actual

Outputs all of RawSnapshotLayer - too much information :)

Stack version

2.3.1

Method of installation

  • Via cabal-install
  • An unofficial package repository: Fedora
@phlummox
Copy link

Yes -- I ran across this issue while trying to work out what was happening in #5326 . verbosity --info gives you literally nothing at all when you execute a minimal

main = print ()

script, but verbosity-debug gives you 456K of output. Surely there's a happy medium between the two...

@mpilgrem
Copy link
Member

See also commercialhaskell/pantry#44.

mpilgrem added a commit that referenced this issue Aug 28, 2022
Fix #5323 New `--no-rsl-in-log` option (by default)
@juhp
Copy link
Contributor Author

juhp commented Aug 30, 2022

Thanks! - will be excited to test this at some point

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