commit | 3e894dc78738791a22e01712bb7f690079c38fbe | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Tue Feb 15 04:05:26 2022 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Tue Feb 15 04:05:26 2022 +0000 |
tree | 34415b09c11820d3531c2fb80c15c31f67c251bd | |
parent | ddf51495681126c7a60ad3d5a4a118ddb9f23e91 [diff] | |
parent | b2486ad9e829b8b175ed96970ccc41d7167b748f [diff] |
Snap for 8183730 from b2486ad9e829b8b175ed96970ccc41d7167b748f to udc-release Change-Id: Ia234c1d61e97cf8002d4faa2f4c0bc57a1055a25
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