diff options
| author | Tavian Barnes <tavianator@tavianator.com> | 2023-11-06 13:08:56 -0500 |
|---|---|---|
| committer | Tavian Barnes <tavianator@tavianator.com> | 2023-11-06 13:08:56 -0500 |
| commit | 79aee58a4621d01c4b1e98c332775f3b87213ddb (patch) | |
| tree | ebaa28d4abd07e7957b17e3dfcdf7ae33e3792c7 /tests/bfs/fprint_duplicate_stdout.out | |
| parent | 7d69fef6a0b80ad57acde7bac8a22b83531fec0d (diff) | |
| download | bfs-79aee58a4621d01c4b1e98c332775f3b87213ddb.tar.xz | |
Treat NO_COLOR="" the same as unset
The docs say
> Command-line software which adds ANSI color to its output by default
> should check for a NO_COLOR environment variable that, when present
> and not an empty string (regardless of its value), prevents the
> addition of ANSI color.
but we were not checking for the empty string.
Link: https://no-color.org/
Link: https://github.com/sharkdp/fd/pull/1421
Diffstat (limited to 'tests/bfs/fprint_duplicate_stdout.out')
0 files changed, 0 insertions, 0 deletions