nu-command 0.115.1

Nushell's built-in commands
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97

//! Nushell pipeline-destination check for custom commands.
//!
//! Complements [`super::is_terminal`]: `is-terminal` is OS `isatty`, while this command
//! reports if a custom command's *return value* is piped, collected, filed, or
//! discarded rather than printed.
//!
//! Implementation relies on [`Stack::is_stdout_redirected`], which reads the
//! invocation-stdout frame pushed in `eval_call` via [`Stack::with_invocation_stdout`].
//!
//! Note: help completion matches substrings of description / extra_description, so
//! avoid accidental tokens like "who" inside common words ("whether", "whole").

use nu_engine::command_prelude::*;

#[derive(Clone)]
pub struct IsRedirected;

impl Command for IsRedirected {
    fn name(&self) -> &str {
        "is-redirected"
    }

    fn signature(&self) -> Signature {
        Signature::build("is-redirected")
            .input_output_type(Type::Nothing, Type::Bool)
            .category(Category::Platform)
    }

    fn description(&self) -> &str {
        "Check if the current custom command's return value is redirected away from display."
    }

    fn extra_description(&self) -> &str {
        "This is a Nushell pipeline-destination check, not an OS TTY check.

Inside a custom command, `is-redirected` reports if that command's return
value will be piped to another command, collected into a value (`let`,
subexpression), written to a file, or discarded — as opposed to being printed
via the normal display path.

Unlike looking at process stdout, this is stable for the entire command body, so
it works inside `if (...)` and `let x = (...)`.

To test if process stdout is a terminal (scripts: `./script | cat`), use
`is-terminal --stdout` instead.

Typical pattern for pretty-vs-data custom commands:

    def mycmd [] {
      if (is-terminal --stdout) and not (is-redirected) {
        # human-friendly formatting
      } else {
        # structured data for pipelines
      }
    }
"
    }

    fn examples(&self) -> Vec<Example<'_>> {
        vec![
            Example {
                description: "Inside a custom command, report if the call's return value is redirected (works in `if`).",
                example: r#"def pipetest [] { if (is-redirected) { "piped" } else { "display" } }; pipetest"#,
                // Display vs redirect depends on how the call is invoked; result omitted.
                result: None,
            },
            Example {
                description: "Return true when the custom command is piped to another command.",
                example: "def pipetest [] { is-redirected }; pipetest | $in",
                result: Some(Value::test_bool(true)),
            },
            Example {
                description: "Return true when the custom command result is collected into a variable.",
                example: "def pipetest [] { is-redirected }; let x = (pipetest); $x",
                result: Some(Value::test_bool(true)),
            },
        ]
    }

    fn search_terms(&self) -> Vec<&str> {
        // Must not be substrings of the command name (see command_context tests).
        vec!["pipe", "pipeline", "display", "stdout", "tty"]
    }

    fn run(
        &self,
        _engine_state: &EngineState,
        stack: &mut Stack,
        call: &Call,
        _input: PipelineData,
    ) -> Result<PipelineData, ShellError> {
        Ok(PipelineData::value(
            Value::bool(stack.is_stdout_redirected(), call.head),
            None,
        ))
    }
}