Maxim Zhiburt

Could you clone the repository and run cargo test? I am assuming that `try_read_after_process_exit` will fail

Could you run `cargo test --no-fail-fast` because some tests were not started because of a single fail.

I see Could you run `try_read_after_process_exit` this test has much smaller scope to investigate. I would expect it will timeouts as well. ``` cargo test -- try_read_after_process_exit ```

Thank you I'll try to work on this tomorrow if you don't mind.

Just for an update. Haven't yet cracked this issue. But I spotted it I hope. It seems like on `macos` process always `is_alive`. And it can't even be stopped.

Once again just for an update, I haven't found a solution for this "bug" yet. But it is 100% related to a core `pty` lib. Only found a similar issue...

So it was a while :) But I guess I figure something out :smile: The issue was not why it doesn't work on `freebsd` and `macos`. But why it works...

related: #3

A research showed - reading changes a terminal line settings: Here use `cargo run --example interact` and type `stty` command. ##### With read before interact ```bash stty^Mspeed 38400 baud; line...

Here's a termios flags differences ```log Termios { inner: RefCell { value: termios { c_iflag: 1024, c_oflag: 5, c_cflag: 191, c_lflag: 35385, c_line: 0, c_cc: [3, 28, 127, 21, 4,...