From: Tom Tromey <tom@tromey.com>
To: Konst Mayer <cdlscpmv@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC 0/8] add terminal styling to gdb
Date: Mon, 25 Mar 2019 15:07:00 -0000 [thread overview]
Message-ID: <8736nbkn7z.fsf@tromey.com> (raw)
In-Reply-To: <20190324102747.GB10967@localhost> (Konst Mayer's message of "Sun, 24 Mar 2019 10:27:47 +0000")
>>>>> "Konst" == Konst Mayer <cdlscpmv@gmail.com> writes:
Konst> I have been very pleased to see that gdb supports colors now. Here
Konst> is some feedback:
Konst> - I propose to rename the 'intensity' setting to 'attributes' which
Konst> among the intensity settings would support additional properties
Konst> like underline, reverse, italic (other properties can be added in the
Konst> future without contradicting the option name).
My intent was to go with something like "set style mumble underline on"
-- that is, let each attribute be specified individually. The main
advantage of this is that completion comes automatically.
I don't care a whole lot about the spelling, though, and it would be
fine if someone wanted to implement it some other way; the existing
command could be deprecated but kept around.
Konst> - Support accepting numbers (in the range 0..255) in addition to names
Konst> when setting foreground/background color.
Supporting 24-bit color, I guess via hex(?), would also be nice.
I'm not sure if I will get around to this or not, but I welcome patches.
Feel free to file bugs for things like this.
Tom
next prev parent reply other threads:[~2019-03-25 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 10:27 Konst Mayer
2019-03-25 15:07 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-06 21:13 Tom Tromey
2018-09-07 6:23 ` Eli Zaretskii
2018-09-07 14:36 ` Tom Tromey
2018-09-07 14:56 ` Eli Zaretskii
2018-09-07 15:01 ` Eli Zaretskii
2018-09-07 7:25 ` Joel Brobecker
2018-10-04 13: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=8736nbkn7z.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cdlscpmv@gmail.com \
--cc=gdb-patches@sourceware.org \
/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