| commit | 89ef2ac669bac99378f2a64e3c1186496631f06e | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Aug 15 23:10:47 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Aug 15 23:10:47 2024 +0000 |
| tree | 364ecfe735d810ea6e08f88e38f33cbf9850be9e | |
| parent | 3da4f0f58586b0a411296a56035ebdaaeb0bad85 [diff] | |
| parent | fbdd0d495e305064929b2ac6f820fcd466b46b53 [diff] |
Snap for 12235414 from fbdd0d495e305064929b2ac6f820fcd466b46b53 to 24Q4-release Change-Id: I0c16e9560c8f156834d300dc492485a9c533c19a
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