tag | 962592f01531b6d0b87a109b615ce91ea09ebbbe | |
---|---|---|
tagger | Xin Li <delphij@google.com> | Wed Apr 24 19:37:48 2024 -0700 |
object | 276dc3baeb994afe584baef057c572dfb4c4f32a |
aml_hef_341613000 (11465779,com.google.android.healthfitness)
commit | 276dc3baeb994afe584baef057c572dfb4c4f32a | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sat Jul 08 04:31:13 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Sat Jul 08 04:31:13 2023 +0000 |
tree | c582cd4a56d60253952c8c33beb566135f5fb6f5 | |
parent | db07cbc279be7eeb86b492d24edd296cee85300c [diff] | |
parent | 5951f6757f2bc2ebffcd3434a3ba5c5d6153f636 [diff] |
Snap for 10460766 from 5951f6757f2bc2ebffcd3434a3ba5c5d6153f636 to mainline-healthfitness-release Change-Id: Ie8b24815da3bd790027ef6c150aa51ffbcf64eff
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