tag | 211f2e12dc569984203fadcc0a9d6b48910a7e4a | |
---|---|---|
tagger | softprops <d.tangren@gmail.com> | Thu Jul 11 23:29:13 2019 |
object | cedd88ac20d8e1ba4feb62ef371ffdf0a2d68e54 |
commit | cedd88ac20d8e1ba4feb62ef371ffdf0a2d68e54 | [log] [tgz] |
---|---|---|
author | softprops <d.tangren@gmail.com> | Thu Jul 11 23:27:41 2019 |
committer | softprops <d.tangren@gmail.com> | Thu Jul 11 23:27:41 2019 |
tree | 81fbb95aec4143285699920377bae9ef39cbb39d | |
parent | a90c50d712ae9f5418ed0eaa0471295eab192d1d [diff] |
upgrade to 2018 edition
are you or are you not a tty?
Add the following to your Cargo.toml
[dependencies] atty = "0.2"
extern crate atty; 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-2017