commit | dc3dd87973c3cb7d558897c2e3d25c6ac5328684 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Aug 31 03:04:30 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue Aug 31 03:04:30 2021 +0000 |
tree | e65d0b1b84b3f3f4b62e32eb27ecae60698a75bd | |
parent | 4ab082269fb3d80dd89bdbd52079083a89354897 [diff] | |
parent | ddf51495681126c7a60ad3d5a4a118ddb9f23e91 [diff] |
Snap for 7688365 from ddf51495681126c7a60ad3d5a4a118ddb9f23e91 to tm-release Change-Id: I122a3d61913fadf09336d67b5dbb270bf94ed9fa
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