tag | 80d6bfd30fd628809bc736cafb73e6a49aa9b680 | |
---|---|---|
tagger | softprops <[email protected]> | Sun Jan 05 22:19:53 2020 |
object | 7b5df17888997d57c2c1c8f91da1db5691f49953 |
commit | 7b5df17888997d57c2c1c8f91da1db5691f49953 | [log] [tgz] |
---|---|---|
author | softprops <[email protected]> | Sun Jan 05 22:09:31 2020 |
committer | softprops <[email protected]> | Sun Jan 05 22:09:31 2020 |
tree | 04c0bf50e96e797d64ea1375614f061be98c7981 | |
parent | 84767e07d5c38f2e81873f7cff20fe8a45484e7d [diff] |
prep release
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