commit | e659cd1afaf0f9deff4c3dead068bd030f8317da | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jan 31 01:50:22 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jan 31 01:50:22 2022 +0000 |
tree | 34415b09c11820d3531c2fb80c15c31f67c251bd | |
parent | 8e3d7343d2b863268a287475dbe5a746830b14ed [diff] | |
parent | 76d094bdee078aebdf05a40bcf2420ca3f950ae4 [diff] |
Snap for 8133678 from 76d094bdee078aebdf05a40bcf2420ca3f950ae4 to t-keystone-qcom-release Change-Id: Iff7afe54bcacd73bcd2ce72a3310c46d3d831162
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