`uru gem <command>` requiring user interaction fails

[Jon]

Gem upgrades (e.g. - uru gem up rake) can require overwrites to existing binfiles and uninstalls (e.g. - uru gem uni minitest) can require identification of specific versions. Rubygems provided prompts and require user responses.

Uru does not currently work well in these scenarios due to how uru creates child processes to do the work. Uru is handling stdin and stdout with the child process in a way that does not work with these scenarios.

[Jon]

As the child process's intermediate output is not shown until after the command exits, investigate pipe semantics rather than simply connecting up stdin to the child process.

Typical failure signature is to appear to hang indefinitely, but in reality the child process has presented a message and is waiting for user input. Since the child message is not currently displayed, user doesn't know child process is awaiting input and thinks the command is hung.

[Jon]

uru and ruby/gem child procs now talk. Closes #51

→ <<cset 815162e4cf96>>