-
Notifications
You must be signed in to change notification settings - Fork 21
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
Default verbosity level #26
Comments
Personally I think that the verbose version should be kept default because it continuously informs the user what is happening which is always good. |
I would argue that the common approach to this from pretty all CLI applications and especially UNIX utilities are that you output only "the results" and have flags like I can imagine use cases like |
for that to set verbosity to 0 would be the way to do, because provide totally silent option is non-sense. |
+1 for automated use there is also the example of |
another perhaps pertinent consideration could be how errors are communicated to the caller in bash, so that we can e.g. retry if upload fails when used in shell scripting |
In case of errors it exits from the application with code |
as I mentioned in my comment #26 (comment) verbosity 0 is for automated usage. nevertheless if it is not intuitive for most of the users, we may introduce an alias for |
In many CLI tools I worked with there was a |
The original issue about default verbosity is fixed, follow the discussion about the new options in #54 |
By default there is a lot of information printed on the console. It would be better to change the default verbosity level to 1 to keep it a bit down. Then if someone needs more information (for example when debugging) they can always set the verbosity level higher.
The text was updated successfully, but these errors were encountered: