| commit | f76b2e3c45f3ebf12c61e7a57bed6e07a1d4a859 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Thu Feb 17 03:29:36 2022 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Thu Feb 17 03:29:36 2022 +0000 |
| tree | 34415b09c11820d3531c2fb80c15c31f67c251bd | |
| parent | bede0583088834c6d07e09a72fbf67f85c6d78cf [diff] | |
| parent | b2486ad9e829b8b175ed96970ccc41d7167b748f [diff] |
Snap for 8191477 from b2486ad9e829b8b175ed96970ccc41d7167b748f to tm-frc-permission-release Change-Id: Id1c92ab06509aba8b043f1c851bbe97aff43c386
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