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 stdout doesn't appear until process exits #1
Comments
ebkalderon
added
the
type: bug
label
Jan 7, 2016
ebkalderon
added this to the 1.0 milestone
Jan 7, 2016
ebkalderon
self-assigned this
Jan 7, 2016
added a commit
that referenced
this issue
Jan 13, 2016
ebkalderon
added
the
diff: easy
label
Jan 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
ebkalderon
Jan 13, 2016
Member
Seems like the Command::stdout() method with Stdio::inherit() passed may fix this problem.
|
Seems like the Command::stdout() method with Stdio::inherit() passed may fix this problem. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Commit 984d03c checks out! Closing this issue. |
ebkalderon
closed this
Jan 13, 2016
ebkalderon
added
status: resolved
pri: blocker
labels
Jan 13, 2016
pushed a commit
to LucioFranco/tools
that referenced
this issue
Mar 23, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ebkalderon commentedJan 7, 2016
When calling any Amethyst subcommand which utilizes the
cargo::call()wrapper, the output doesn't appear immediately on the screen.This is because std::process::Command works like this by design, buffering the output until the process exits and then displays it all at once on the screen. Eventually, we need to find an alternative library or design that allows immediate display of stdout/stderr as the process runs.
I'm classifying this as a bug, as it makes the command very irritating from a UX point of view. This must be fixed before 1.0.