nushell/crates/nu-command
Eric Hodel d5677625a7
Add is-terminal to determine if stdin/out/err are a terminal ()
# Description

I'm not sure if "is-terminal" is the best name for this command as there
is also "term size". Uses
[`is_terminal()`](https://doc.rust-lang.org/stable/std/io/trait.IsTerminal.html#tymethod.is_terminal)
which is cross-platform.

Possible alternative names:
* `term is-tty --stdout`
* `term is-tty stdout`
* `term is-terminal stdout`

If multiple streams are provided an error is returned. The error span
covers all arguments as the incompatible one is not known. This may be
new?

Fixes 

# User-Facing Changes

* Add `is-terminal` to check if stdin, stdout, or stderr are a terminal
(TTY)

# Tests + Formatting

The nu tests always redirect stdin, stdout, and stderr so a positive
test case is not possible without extra work

- 🟢 `toolkit fmt`
- 🟢 `toolkit clippy`
- 🟢 `toolkit test`
- 🟢 `toolkit test stdlib`

# After Submitting

The new command will be added automatically

---------

Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
2023-11-21 20:48:39 -06:00
..
src Add is-terminal to determine if stdin/out/err are a terminal () 2023-11-21 20:48:39 -06:00
tests Add is-terminal to determine if stdin/out/err are a terminal () 2023-11-21 20:48:39 -06:00
Cargo.toml Bump procfs to 0.16.0 () 2023-11-20 21:22:35 +01:00
LICENSE Fix rest of license year ranges () 2023-04-04 09:03:29 +12:00