commit | 5b1b771eb9d1aafe20d45c7595bff233b4b5e8cc | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Thu Feb 17 03:34:39 2022 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Thu Feb 17 03:34:39 2022 +0000 |
tree | 34415b09c11820d3531c2fb80c15c31f67c251bd | |
parent | a3e56201eca95025f2b01a359289c844484d497d [diff] | |
parent | b2486ad9e829b8b175ed96970ccc41d7167b748f [diff] |
Snap for 8191477 from b2486ad9e829b8b175ed96970ccc41d7167b748f to tm-frc-scheduling-release Change-Id: I5ba52c5efccdd8dd6e85e25b8368310eda747a6e
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