You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
jianglk.darker 7ee447c011
v811_spc009_project
4 months ago
..
examples v811_spc009_project 4 months ago
src v811_spc009_project 4 months ago
.cargo_vcs_info.json v811_spc009_project 4 months ago
Android.bp v811_spc009_project 4 months ago
CHANGELOG.md v811_spc009_project 4 months ago
Cargo.toml v811_spc009_project 4 months ago
Cargo.toml.orig v811_spc009_project 4 months ago
LICENSE v811_spc009_project 4 months ago
METADATA v811_spc009_project 4 months ago
MODULE_LICENSE_MIT v811_spc009_project 4 months ago
OWNERS v811_spc009_project 4 months ago
README.md v811_spc009_project 4 months ago
rustfmt.toml v811_spc009_project 4 months ago

README.md

atty

Build Status Build status Coverage Status crates.io Released API docs Master API docs

are you or are you not a tty?

install

Add the following to your Cargo.toml

[dependencies]
atty = "0.2"

usage

use atty::Stream;

fn main() {
  if atty::is(Stream::Stdout) {
    println!("I'm a terminal");
  } else {
    println!("I'm not");
  }
}

testing

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