Handle the --color flag via proper global state #6743
Merged
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.
Use
color.NoColor
as a global progressively modified as one descendsdown command flags. Allows non-surprising operation when --color is
accepted at multiple layers, and even makes this behave predictably:
Thanks to @stuberman for poking me about the current state being non-ideal, and to @iand for prompting me to reexamine how we do things
P.S. GNU-getopt 4EVAH‼️