| commit | 0340e8b3b8652332740af48e7da650ab66cbf7e7 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Thu Mar 14 18:11:04 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Thu Mar 14 18:11:04 2024 +0000 |
| tree | 8a2f8ca02a855a7e6380a49522514fc34d302757 | |
| parent | 85614217d0f7114c6a2facb7c4fc24b5155f7366 [diff] | |
| parent | 4ea1424c923562895ab5f32af0d2fb128e19e2c8 [diff] |
Snap for 11574415 from 4ea1424c923562895ab5f32af0d2fb128e19e2c8 to emu-35-1-release Change-Id: I6b73199681a45744f3af973273bf09b523f7271d
are you or are you not a tty?
Add the following to your Cargo.toml
[dependencies] atty = "0.2"
use atty::Stream; fn main() { if atty::is(Stream::Stdout) { println!("I'm a terminal"); } else { println!("I'm not"); } }
This library has been unit tested on both unix and windows platforms (via appveyor).
A simple example program is provided in this repo to test various tty's. By default.
It prints
$ cargo run --example atty stdout? true stderr? true stdin? true
To test std in, pipe some text to the program
$ echo "test" | cargo run --example atty stdout? true stderr? true stdin? false
To test std out, pipe the program to something
$ cargo run --example atty | grep std stdout? false stderr? true stdin? true
To test std err, pipe the program to something redirecting std err
$ cargo run --example atty 2>&1 | grep std stdout? false stderr? false stdin? true
Doug Tangren (softprops) 2015-2019