public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrei Pikas <gdb@mail.api.win>
Cc: gdb-patches@sourceware.org, gdb@mail.api.win
Subject: Re: [PATCH] Add an option with a color type.
Date: Wed, 17 Aug 2022 20:57:31 +0300	[thread overview]
Message-ID: <83fshuda7o.fsf@gnu.org> (raw)
In-Reply-To: <20220815211534.33740-1-gdb@mail.api.win> (message from Andrei Pikas on Tue, 16 Aug 2022 00:15:34 +0300)

> From: Andrei Pikas <gdb@mail.api.win>
> Date: Tue, 16 Aug 2022 00:15:34 +0300
> Cc: Andrei Pikas <gdb@mail.api.win>
> 
> Colors can be specified as name of one of the basic colors "none", "black",
> "white", etc., as a number up to 255, or as RGB hexadecimal tripplet #RRGGBB.
> ---
>  gdb/NEWS                         |   3 +
>  gdb/cli/cli-cmds.c               |   8 ++
>  gdb/cli/cli-decode.c             | 200 +++++++++++++++++++++++++++++++
>  gdb/cli/cli-decode.h             |  30 +++++
>  gdb/cli/cli-option.c             |  42 +++++++
>  gdb/cli/cli-option.h             |  21 ++++
>  gdb/cli/cli-setshow.c            |  53 ++++++++
>  gdb/cli/cli-setshow.h            |   6 +
>  gdb/cli/cli-style.c              |  49 ++------
>  gdb/cli/cli-style.h              |   4 +-
>  gdb/command.h                    |  26 +++-
>  gdb/guile/scm-param.c            |  69 ++++++++++-
>  gdb/python/py-param.c            |  63 +++++++++-
>  gdb/python/python.c              |  18 +++
>  gdb/testsuite/gdb.base/style.exp |  15 +++
>  gdb/ui-style.h                   |  16 ++-
>  16 files changed, 575 insertions(+), 48 deletions(-)
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index d2efe2a0a58..5234d4f8501 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -55,6 +55,9 @@
>    Python Pygments is still used.  For supported targets, libopcodes
>    styling is used by default.
>  
> +  "set style" commands now supports numeric format for basic colors
> +  from -1 to 255 and #RRGGBB format for truecolor.
> +
>  * New commands

OK for the NEWS part.

Thanks.

      parent reply	other threads:[~2022-08-17 17:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 21:15 Andrei Pikas
2022-08-17 17:40 ` Andrew Burgess
2022-08-17 18:46   ` Andrei Pikas
2022-08-20 12:19   ` [PATCH v2] " Andrei Pikas
2022-08-20 12:43     ` Eli Zaretskii
2022-08-21 20:09       ` Andrei Pikas
2022-08-22  2:26         ` Eli Zaretskii
2022-08-21 21:07       ` [PATCH v3 (documentation fixed)] " Andrei Pikas
2022-08-22 11:54         ` Eli Zaretskii
2022-08-22 16:26           ` Philippe Waroquiers
2022-08-23 11:29         ` Andrew Burgess
2022-09-13  0:44           ` [PATCH v4 (documentation + approximation + convenience variable + python and guile types)] " Andrei Pikas
2022-08-17 17:57 ` Eli Zaretskii [this message]

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=83fshuda7o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@mail.api.win \
    /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).