commit | 7fe26dfe088dab473d7223e84b4fc74a3ab0b3c7 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Wed Mar 17 01:04:20 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Mar 17 01:04:20 2021 +0000 |
tree | c1323664297e3a6551ede88c2465d58d8f4f6b60 | |
parent | c46616738591f7bcaee466cd2db36af5cab4775f [diff] | |
parent | e41109e02fd052be5dd6a4a264cd203bbf65410d [diff] |
Snap for 7213262 from e41109e02fd052be5dd6a4a264cd203bbf65410d to sc-d1-release Change-Id: I7147b1508c5d5701372f24525f1f88bfc41bce51
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