2019-05-21 18:56:39 +03:00
|
|
|
//! This is a conceptually simple example that spawns the `whoami` program
|
|
|
|
//! to print your username. It is made more complex because there are multiple
|
|
|
|
//! pipes involved and it is easy to get blocked/deadlocked if care and attention
|
|
|
|
//! is not paid to those pipes!
|
2020-01-20 04:32:33 +03:00
|
|
|
use portable_pty::{CommandBuilder, NativePtySystem, PtySize, PtySystem};
|
2019-05-20 17:20:47 +03:00
|
|
|
|
|
|
|
fn main() {
|
2020-01-20 04:32:33 +03:00
|
|
|
let pty_system = NativePtySystem::default();
|
2019-05-20 17:20:47 +03:00
|
|
|
|
2019-06-09 17:33:00 +03:00
|
|
|
let pair = pty_system
|
2019-05-20 17:20:47 +03:00
|
|
|
.openpty(PtySize {
|
|
|
|
rows: 24,
|
|
|
|
cols: 80,
|
|
|
|
pixel_width: 0,
|
|
|
|
pixel_height: 0,
|
|
|
|
})
|
|
|
|
.unwrap();
|
|
|
|
|
|
|
|
let cmd = CommandBuilder::new("whoami");
|
2019-06-09 17:33:00 +03:00
|
|
|
let mut child = pair.slave.spawn_command(cmd).unwrap();
|
2019-05-21 18:56:39 +03:00
|
|
|
// Release any handles owned by the slave: we don't need it now
|
|
|
|
// that we've spawned the child.
|
2019-06-09 17:33:00 +03:00
|
|
|
drop(pair.slave);
|
2019-05-20 17:20:47 +03:00
|
|
|
|
2020-01-20 18:55:11 +03:00
|
|
|
let mut reader = pair.master.try_clone_reader().unwrap();
|
2019-05-21 18:56:39 +03:00
|
|
|
// We hold handles on the pty. Now that the child is complete
|
|
|
|
// there are no processes remaining that will write to it until
|
|
|
|
// we spawn more. We're not going to do that in this example,
|
|
|
|
// so we should close it down. If we didn't drop it explicitly
|
|
|
|
// here, then the attempt to read its output would block forever
|
|
|
|
// waiting for a future child that will never be spawned.
|
2019-06-09 17:33:00 +03:00
|
|
|
drop(pair.master);
|
2019-05-21 18:56:39 +03:00
|
|
|
|
|
|
|
// Consume the output from the child
|
2020-01-20 18:55:11 +03:00
|
|
|
let mut s = String::new();
|
|
|
|
reader.read_to_string(&mut s).unwrap();
|
2019-05-21 18:56:39 +03:00
|
|
|
|
|
|
|
// We print with escapes escaped because the windows conpty
|
|
|
|
// implementation synthesizes title change escape sequences
|
|
|
|
// in the output stream and it can be confusing to see those
|
|
|
|
// printed out raw in another terminal.
|
|
|
|
print!("output: ");
|
|
|
|
for c in s.escape_debug() {
|
|
|
|
print!("{}", c);
|
|
|
|
}
|
2020-09-25 19:20:22 +03:00
|
|
|
|
|
|
|
// Note that we're waiting until after we've read the output
|
|
|
|
// to call `wait` on the process.
|
|
|
|
// On macOS Catalina, waiting on the process seems to prevent
|
|
|
|
// its output from making it into the pty.
|
|
|
|
println!("child status: {:?}", child.wait().unwrap());
|
2019-05-20 17:20:47 +03:00
|
|
|
}
|