Skip to content
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

Add a --supress-messages global option to turn off all task io messages. #396

Merged
merged 1 commit into from
Aug 3, 2016

Conversation

greg-1-anderson
Copy link
Member

Related to #383, this gives users a way to turn off Robo messages -- which is to say, anything produced by TaskIO.

@greg-1-anderson
Copy link
Member Author

greg-1-anderson commented Aug 1, 2016

Note that output produced by say et. al. are not affected. Use --quiet to get rid of all output.

Also, this PR does not supress error and warning messages, as those are important and should probably always be shown. This behavior is open to discussion, though.

@greg-1-anderson greg-1-anderson added this to the 1.0 milestone Aug 2, 2016
@DavertMik
Copy link
Member

Ok, that makes sense. But we have too much levels of hiding here :(

--quiet, --supress-messages, etc

So it could be like the opposite to verbosity --quiet, --very-quiet, --very-very-quiet, or -q, -vq, -vvq
Not the best naming and I don't have ideas for better ones. So let's stick with current behavior )

@DavertMik DavertMik merged commit ef259b6 into master Aug 3, 2016
greg-1-anderson added a commit that referenced this pull request Sep 22, 2016
…this option is not sufficiently different than --quiet. Applications that wish to alter the way that Robo handles status messages should override Robo's default container as described in docs/framework.md.
greg-1-anderson added a commit that referenced this pull request Sep 23, 2016
@greg-1-anderson greg-1-anderson deleted the supress-messages branch October 17, 2019 04:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants