commit | bc632e1b180a522d43cdade566edea61fc683d86 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Wed Mar 24 01:04:15 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Mar 24 01:04:15 2021 +0000 |
tree | 505dc9520d1851452ff862429424cff9418e96d0 | |
parent | 7fe26dfe088dab473d7223e84b4fc74a3ab0b3c7 [diff] | |
parent | 670197b0e600fd0290a3e89f67ebd5071af6b445 [diff] |
Snap for 7230642 from 670197b0e600fd0290a3e89f67ebd5071af6b445 to sc-d1-release Change-Id: I69a3cd833c98ef679efa34dbaf182a875ce7b7f8
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