tag	2b1de2a24d93a68b098971fb21fcc9e6e33bf830
tagger	The Android Open Source Project <initial-contribution@android.com>	Tue Mar 28 12:25:51 2023 -0700
object	0e18329b46c608ce27f1605b0e275d84b0860dee

commit	0e18329b46c608ce27f1605b0e275d84b0860dee	[log] [tgz]
author	Android Build Coastguard Worker <android-build-coastguard-worker@google.com>	Mon May 09 20:35:18 2022 +0000
committer	Android Build Coastguard Worker <android-build-coastguard-worker@google.com>	Mon May 09 20:35:18 2022 +0000
tree	34415b09c11820d3531c2fb80c15c31f67c251bd
parent	661839d15234a38d1db1aa2da52d5766cf130f53 [diff]
parent	b2486ad9e829b8b175ed96970ccc41d7167b748f [diff]

tree: 34415b09c11820d3531c2fb80c15c31f67c251bd

README.md

atty

are you or are you not a tty?

install

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