distinguish -q and -qq #12300
Open
distinguish -q and -qq #12300
+153
−54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gankra
added
the
enhancement
|
Also worth noting here that any distinction we do introduce is, strictly speaking, a breaking change. As someone could have been relying on |
zanieb
reviewed
Mar 21, 2025
| pub quiet: bool, | ||
| /// Use quiet output. | ||
| /// | ||
| /// `-q` will produce less stdout output while `-qq` will produce no stdout output. |
There was a problem hiding this comment.
Should we avoid updating this for now and track once we start using it?
I would start with
Suggested change
| /// `-q` will produce less stdout output while `-qq` will produce no stdout output. | |
| /// Repeating this option, e.g., `-qq`, will enable a silent mode in which uv will write no output to stdout. |
zanieb
approved these changes
Mar 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea here is that we introduce a new stdout_important method for things that want to care about the difference between "quiet" and "silent".
This PR is WIP because it has no actual uses of stdout_important, and we should have at least one before landing this. Perhaps someone has a suggestion for commands that would really benefit from this distinction?
Fixes #10431