8000 Don't write to stderr when there are no errors · Issue #22 · tommy351/tsc-multi · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Don't write to stderr when there are no errors #22

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.

Sign up for GitHub

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

Jump to bottom
Open
tylerbutler opened this issue Nov 9, 2023 · 1 comment
Open

Don't write to stderr when there are no errors #22

tylerbutler opened this issue Nov 9, 2023 · 1 comment

Comments

@tylerbutler
Copy link

tsc-multi writes to stderr even when it just says "Found 0 e 88FA rrors". It should use stdout in the success case.
@tylerbutler tylerbutler mentioned this issue Nov 9, 2023
Merged
@niieani
Copy link
niieani commented Feb 10, 2024 •
edited
Loading

The unix philosophy generalizes stderr for writing information about errors, not necessarily just errors themselves. Check out how tools like curl use stderr for diagnostic output (progress meters, and other diagnostic information all go to stderr).
stdout is usually reserved for output that is meant to be piped to other tools.

From wikipedia:

Standard error is another output stream typically used by programs to output error messages or diagnostics.

I think the current behavior is fine, since "Found 0 errors" qualifies as a diagnostic message in my view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tylerbutler @niieani
0