commit | 1f2dfac758a5002f008c1c9ede9819fd45cbf3af | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed May 10 16:16:16 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed May 10 16:16:16 2023 +0000 |
tree | c582cd4a56d60253952c8c33beb566135f5fb6f5 | |
parent | b2486ad9e829b8b175ed96970ccc41d7167b748f [diff] | |
parent | 5951f6757f2bc2ebffcd3434a3ba5c5d6153f636 [diff] |
Snap for 10103804 from 5951f6757f2bc2ebffcd3434a3ba5c5d6153f636 to mainline-tzdata5-release Change-Id: I216ea86fd12aea154bf79f975136e13e16950d9d
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