From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 6/8] Introduce metadata style
Date: Mon, 30 Sep 2019 14:07:00 -0000 [thread overview]
Message-ID: <a32f076b-0681-a2e6-3f77-d94970f696bb@redhat.com> (raw)
In-Reply-To: <20190927212520.20073-7-tom@tromey.com>
On 9/27/19 10:25 PM, Tom Tromey wrote:
> @@ -372,4 +376,11 @@ Highlight display styling.\n\
> Configure highlight colors and display intensity\n\
> Some commands use the highlight style to draw the attention to a part\n\
> of their output."));
> +
> + STYLE_ADD_SETSHOW_COMMANDS (metadata_style,
> + _("\
> +Metadata display styling\n\
> +Configure metadata colors and display intensity\n\
> +The \"metadata\" style is used when GDB displays information about\n\
> +your data, for example \"<unavailable\""));
Missing ">" in "<unavailable>".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-09-30 14:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:25 [PATCH 0/8] More gdb styling improvements Tom Tromey
2019-09-27 21:25 ` [PATCH 2/8] Don't create empty literal pieces Tom Tromey
2019-09-27 21:25 ` [PATCH 5/8] Style "pwd" output Tom Tromey
2019-09-27 21:25 ` [PATCH 3/8] Introduce gdb-specific %p format suffixes Tom Tromey
2019-09-30 14:06 ` Pedro Alves
2021-08-18 9:02 ` Andreas Schwab
2021-08-27 20:17 ` Tom Tromey
2019-09-27 21:25 ` [PATCH 7/8] Use styled_string in more places Tom Tromey
2019-09-27 21:25 ` [PATCH 6/8] Introduce metadata style Tom Tromey
2019-09-30 14:07 ` Pedro Alves [this message]
2019-09-27 21:25 ` [PATCH 4/8] Use new %p format suffixes in gdb Tom Tromey
2019-09-30 14:05 ` Pedro Alves
2019-09-27 21:25 ` [PATCH 8/8] Use styled_string for "show logging filename" Tom Tromey
2019-09-27 21:25 ` [PATCH 1/8] Remove the ui_out_style_kind enum Tom Tromey
2019-09-30 14:09 ` [PATCH 0/8] More gdb styling improvements Pedro Alves
2019-10-01 21:11 ` Tom Tromey
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=a32f076b-0681-a2e6-3f77-d94970f696bb@redhat.com \
--to=palves@redhat.com \
--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