commit | aeeda1f57af858136947b7ec54c17152a9a4233a | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 10 05:14:31 2023 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Mar 10 05:14:31 2023 +0000 |
tree | c582cd4a56d60253952c8c33beb566135f5fb6f5 | |
parent | 242951e7d22cb971960511415b7adeda38ec10f8 [diff] | |
parent | 79b502426ef9764f1dbcc7b740ed7d2100bc453d [diff] |
Snap for 9722771 from 79b502426ef9764f1dbcc7b740ed7d2100bc453d to udc-d1-release Change-Id: Ia2147980e9833d456afa0b5c339bc94c80da7f02
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