-
Notifications
You must be signed in to change notification settings - Fork 34
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
Errors should go to stderr #40
Comments
I'm still seeing this behavior:
From an interface perspective, I think it would be more clear and less error-prone if the command took an explicit file input, something like:
Otherwise I agree that putting warnings and errors to stderr instead of stdout helps clarify issues. |
I think that this is probably correct behaviour because What I don't understand, and this may be my fault, is when the usage output says:
when this doesn't/shouldn't apply to |
I accidentally ran:
when I should have used
-H
. The error output went to stdout and got redirected tox.rb
.The text was updated successfully, but these errors were encountered: