-
Notifications
You must be signed in to change notification settings - Fork 477
Rewatch: log errors to stderr #8147
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
Conversation
| .build(); | ||
|
|
||
| log::set_max_level(log_level_filter); | ||
| log::set_boxed_logger(Box::new(SplitLogger { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems there is no better way with env_logger.
rescript
@rescript/darwin-arm64
@rescript/darwin-x64
@rescript/linux-arm64
@rescript/linux-x64
@rescript/runtime
@rescript/win32-x64
commit: |
|
Regardless of what bsb does, can you elaborate why this is better or what problem this solved? |
|
It is standard behavior of Unix CLI tools to write output to stdout and errors to stderr, allowing for separate redirection of output stream and error stream. So as a user I would expect that behavior, and I would expect a very good reason for deviation, especially if the old build system followed standards here. |
Fixes #8138