commit | 4d0df6bfcaca30df4b97a743f851c4caa7a2e5b4 | [log] [tgz] |
---|---|---|
author | Linux Build Service Account <lnxbuild@localhost> | Sun Jan 16 14:27:19 2022 -0800 |
committer | Linux Build Service Account <lnxbuild@localhost> | Sun Jan 16 14:27:19 2022 -0800 |
tree | 505dc9520d1851452ff862429424cff9418e96d0 | |
parent | 3418db2571da9178ce09f630401bfc88923820d4 [diff] | |
parent | f6a39426972d7fea7e6297204f2271dd5b098725 [diff] |
Merge f6a39426972d7fea7e6297204f2271dd5b098725 on remote branch Change-Id: Icf2e4e00b986ecea13040455036ec9018c68dc4b
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