| commit | 8bcaa4c9644718bfc025c2295817200056e16f9d | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Tue Sep 10 23:08:24 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Tue Sep 10 23:08:24 2024 +0000 |
| tree | 364ecfe735d810ea6e08f88e38f33cbf9850be9e | |
| parent | d8b12e455b16c2e91aed02eb8ff2ea29e993e43e [diff] | |
| parent | cb0b7352d2e31254f0a1005137fea9b88e93b0f0 [diff] |
Snap for 12349386 from cb0b7352d2e31254f0a1005137fea9b88e93b0f0 to sdk-release Change-Id: Ibf55f0cea5b1e43e2b446d331fac1ed381ed67f8
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