Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upCargo stderr only prints after stdout #7
Comments
ebkalderon
added
type: bug
diff: medium
pri: normal
labels
Feb 10, 2016
ebkalderon
self-assigned this
Feb 10, 2016
ebkalderon
added this to the 1.0 milestone
Feb 10, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ebkalderon
Feb 11, 2016
Member
Unfortunately, I can't find an equivalent to std::process::Stdio::inherit() that works with stderr output. If anyone knows of a good alternative, please mention it here.
|
Unfortunately, I can't find an equivalent to |
added a commit
that referenced
this issue
Feb 11, 2016
ebkalderon
referenced this issue
Feb 11, 2016
Merged
Properly print errors and warnings from Cargo #11
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Fixed by pull request #11. Closing. |
ebkalderon
closed this
Feb 11, 2016
ebkalderon
added
the
status: resolved
label
Feb 11, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ebkalderon commentedFeb 10, 2016
The current behavior of the
execute_if!()macro in theamethyst_clitool is to print out error text (unformatted) immediately before quitting the program. Though this is perfectly fine for most cases, this can make redirected Cargo output fromamethyst new,amethyst build,amethyst run, etc. print out at the wrong times, and also lacking colorization.A likely solution would be to make the Cargo stderr print out alongside the stdout using an approach similar to that used to resolve issue #1. We can then have
execute_if!()print out anyamethyst_clispecific errors, like compressing resources and the like.