commit | 9278ef9364afc14bd1ac4f94d39cd0dbc30bbccb | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Wed Dec 15 16:43:38 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Dec 15 16:43:38 2021 +0000 |
tree | 34415b09c11820d3531c2fb80c15c31f67c251bd | |
parent | fbfa43eb4d8e93ed9935508b246d10e00111a87f [diff] | |
parent | b0071d81965a5609d058d3ace4f0fb90ee0cbf08 [diff] |
Merge "Refresh Android.bp, cargo2android.json, TEST_MAPPING." am: 76222effb2 am: b0071d8196 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/atty/+/1912619 Change-Id: I0c96fa503da0b3ada2ac1ffd4da4b08c32d485ab
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