-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Quieter build output #9724
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Comments
opeik
added
the
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
label
Jul 25, 2021
Thanks for the suggestion! I think we generally agree that it would be nice to avoid too much verbose output. However, we generally try to avoid adding too many options for adjusting settings like that. I'm going to close, as I think this is essentially a duplicate of #8889, and I think it would be best to keep the discussion of changing the output in one place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-feature-request
Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Hi there,
Describe the problem you are trying to solve
One of the few issues I have with Cargo is the amount of output on a typical
cargo build
invocation. The line per crate is built is pretty to look at but consumes my terminal.Describe the solution you'd like
A
--progress={bar | full}
flag or something to that effect would be nice. Thebar
option would only display the progress bar. Thefull
option would be the current behaviour, one line per crate as well as the progress bar. It would also be nice to be able to set this globally viaCargo.toml
.Notes
I was thinking of implementing this feature and opening a full request. Related to #8889 (overhauling the entire output).
The text was updated successfully, but these errors were encountered: