commit | 739bd6f4d4f6e835aef8a4fff07ded3f2ecd1846 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Wed Feb 16 08:19:45 2022 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Wed Feb 16 08:19:45 2022 +0000 |
tree | 505dc9520d1851452ff862429424cff9418e96d0 | |
parent | b2486ad9e829b8b175ed96970ccc41d7167b748f [diff] | |
parent | 661839d15234a38d1db1aa2da52d5766cf130f53 [diff] |
Snap for 8189365 from 661839d15234a38d1db1aa2da52d5766cf130f53 to tm-frc-resolv-release Change-Id: I7603285e39497415b9d26807336578ef497d5183
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