StdIo: Honor NO_COLOR environment variable

This convention is documented by https://bixense.com/clicolors/

Closes: #26458
This commit is contained in:
Brad King
2025-05-20 11:51:06 -04:00
parent 27f375d514
commit 6aa604ef10
6 changed files with 36 additions and 7 deletions
+5 -4
View File
@@ -9,11 +9,12 @@ Set to a non-empty value, other than ``0``, to tell command-line
tools to print color messages even if not connected to a terminal.
This is a `common convention`_ among command-line tools in general.
See also the :envvar:`CLICOLOR` environment variable.
:envvar:`!CLICOLOR_FORCE`, if activated, takes precedence over
:envvar:`CLICOLOR`.
See also the :envvar:`NO_COLOR` and :envvar:`CLICOLOR` environment variables.
If :envvar:`NO_COLOR` is activated, it takes precedence over
:envvar:`!CLICOLOR_FORCE`. Otherwise, if :envvar:`!CLICOLOR_FORCE` is
activated, it takes precedence over :envvar:`CLICOLOR`.
See the :variable:`CMAKE_COLOR_DIAGNOSTICS` variable to control
color in a generated build system.
.. _`common convention`: https://web.archive.org/web/20230417221418/https://bixense.com/clicolors/
.. _`common convention`: https://web.archive.org/web/20250410160803/https://bixense.com/clicolors/