commit | 8e3d7343d2b863268a287475dbe5a746830b14ed | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Oct 28 17:29:34 2021 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Oct 28 17:29:34 2021 +0000 |
tree | e65d0b1b84b3f3f4b62e32eb27ecae60698a75bd | |
parent | b6505d4438e3b7b0c6b6a9da33ddacd2f2e004d1 [diff] | |
parent | ea24d194599a190d6c390408d0c9c011eb63d11f [diff] |
Snap for 7862349 from ea24d194599a190d6c390408d0c9c011eb63d11f to t-keystone-qcom-release Change-Id: I49bb8285ebfb4970cf54c20af2f8106d07b34b6a
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