commit | 81e25d41ff78833f2bed88e0633d7f0587b4bd11 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Sat May 11 01:11:36 2024 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Sat May 11 01:11:36 2024 +0000 |
tree | 21afd51725565941ceb3605de2444ddbbd847969 | |
parent | 4ea1424c923562895ab5f32af0d2fb128e19e2c8 [diff] | |
parent | c8f07f738532f7b13277176b61d95bf111e97b4c [diff] |
Snap for 11828632 from c8f07f738532f7b13277176b61d95bf111e97b4c to 24Q3-release Change-Id: Ie42d2c7b2034b88f72c68ddbafe7e686708413a2
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