From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support the NO_COLOR environment variable
Date: Sat, 16 Sep 2023 08:34:33 +0300 [thread overview]
Message-ID: <83bke2k7fa.fsf@gnu.org> (raw)
In-Reply-To: <20230916000908.110459-1-tom@tromey.com> (message from Tom Tromey on Fri, 15 Sep 2023 18:09:08 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Fri, 15 Sep 2023 18:09:08 -0600
> I ran across this site:
>
> https://no-color.org/
>
> ... which lobbies for tools to recognize the NO_COLOR environment
> variable and disable any terminal styling when it is seen.
>
> This patch implements this for gdb.
Should we also support the --color command-line argument, e.g. to
countermand NO_COLOR in the environment, and also as an alternative to
the environment variable?
> ---
> gdb/NEWS | 4 ++++
> gdb/doc/gdb.texinfo | 3 +++
> gdb/main.c | 4 ++++
> gdb/testsuite/gdb.base/early-init-file.exp | 3 ++-
> .../gdb.base/style-interp-exec-mi.exp | 3 ++-
> gdb/testsuite/gdb.base/style-logging.exp | 3 ++-
> gdb/testsuite/gdb.base/style.exp | 9 ++++++---
> .../build-id-no-debug-warning.exp | 3 ++-
> gdb/testsuite/gdb.debuginfod/crc_mismatch.exp | 3 ++-
> gdb/testsuite/gdb.python/py-format-string.exp | 3 ++-
> gdb/testsuite/gdb.python/py-source-styling.exp | 3 ++-
> gdb/testsuite/gdb.python/py-startup-opt.exp | 3 ++-
> gdb/testsuite/gdb.rust/rust-style.exp | 3 ++-
> gdb/testsuite/gdb.tui/tui-layout.exp | 18 +++++++++++-------
> gdb/testsuite/lib/gdb.exp | 2 +-
> gdb/testsuite/lib/tuiterm.exp | 3 ++-
> 16 files changed, 49 insertions(+), 21 deletions(-)
Thanks, the documentation parts of this are approved.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-09-16 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 0:09 Tom Tromey
2023-09-16 5:34 ` Eli Zaretskii [this message]
2023-09-16 8:39 ` Matt Rice
2023-09-16 8:50 ` Eli Zaretskii
2023-09-19 14:11 ` Tom Tromey
2023-09-18 10:03 ` Andrew Burgess
2023-09-19 14:13 ` Tom Tromey
2023-09-26 13:48 ` Andrew Burgess
2024-01-04 0:38 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bke2k7fa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).