fix: matching of the "f" cli option to the fast var#111
Merged
besendorf merged 1 commit intoJul 17, 2026
Conversation
Collaborator
|
Thanks. So theres definatly a mistake there but Im not sure that this is the right solution: maybe we use v for verbose and also call it verbose mode and f for fast mode? |
Contributor
Author
Looking at the current code this seems right: flag.BoolVar(&verbose, "verbose", false, "Verbose mode")
flag.BoolVar(&verbose, "v", false, "Verbose mode")
flag.BoolVar(&fast, "fast", false, "Fast mode")
flag.BoolVar(&fast, "f", false, "Fast mode") |
Collaborator
|
Ah yeah sorry youre right. Thanks! |
This file contains hidden or 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
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 current cli option
fenables verbose output. This PR changes this to the properfastvar.