commit | 96f37805c87532be92c0e226bf6b1b3bcf8ecad0 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Tue May 21 23:12:10 2024 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Tue May 21 23:12:10 2024 +0000 |
tree | e8e6d339337e7fbc75e4f79520dacf12a05635e1 | |
parent | 81e25d41ff78833f2bed88e0633d7f0587b4bd11 [diff] | |
parent | 332011d1cba323324cb6d297d80706ea7df77564 [diff] |
Snap for 11869550 from 332011d1cba323324cb6d297d80706ea7df77564 to 24Q3-release Change-Id: I7e9e84c43373001db3c35f806ad7d6f534a69178
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