You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
std::io::Command by default creates new stdout/stderr for the command.
I don't see an obvious way to make it use same stdout/stderr as the parent process. Could you add an example that shows how to this?
Typically own stdout/stderr is a very desirable behavior, but in Cargo build scripts this hides output of commands and makes debugging difficult, so in that context inherited stdin/stdout is a common and useful use-case.
The text was updated successfully, but these errors were encountered:
/// * Inherit stdin/stdout/stderr for `run` or `status`, but create pipes for `output`
so this behavior has changed to be the default. Therefore, I'm giving this a close. Of course, I plan on adding tons of examples, but this specific one is addressed already.
std::io::Command
by default creates new stdout/stderr for the command.I don't see an obvious way to make it use same stdout/stderr as the parent process. Could you add an example that shows how to this?
Typically own stdout/stderr is a very desirable behavior, but in Cargo build scripts this hides output of commands and makes debugging difficult, so in that context inherited stdin/stdout is a common and useful use-case.
The text was updated successfully, but these errors were encountered: