From: Robert Dewar <dewar@adacore.com>
To: Matt Rice <ratmice@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>,
Kevin Pouget <kevin.pouget@gmail.com>,
Surya Kiran Gullapalli <suryakiran.gullapalli@gmail.com>,
gdb@sourceware.org
Subject: Re: Colors in gdb
Date: Sun, 20 Jan 2013 15:29:00 -0000 [thread overview]
Message-ID: <50FC0D53.7020403@adacore.com> (raw)
In-Reply-To: <CACTLOFqzPJYvdKcF3XjrJ5S2zztztE2XSMvXmW89xf5n8RGj8Q@mail.gmail.com>
On 1/20/2013 10:13 AM, Matt Rice wrote:
> maybe i'm old in not liking the idea of making these work with the
> standard 'print' command, because the escape sequences are terminal
> type dependent, which is IMO fine for a prompt set by a gdbinit, but
> less so for a pretty printer distributed with a library...
> this opinion is only strengthened by considering a std::string
> containing an escape sequence.
I strongly dislike ANY color stuff creeping into gdb output. Color
stuff is a big menace when stuff is saved to files, or pasted and
emailed etc etc.
> i'm fairly steadfast that just having random escape sequences embedded
> in pretty printers as i implemented it is entirely the wrong thing to
> do, and we need some level of indirection that can be set in .gdbinit
> that pretty printers can query
I agree
next prev parent reply other threads:[~2013-01-20 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 13:59 Surya Kiran Gullapalli
2013-01-10 20:50 ` psyprus
2013-01-15 17:48 ` Tom Tromey
2013-01-15 18:47 ` Kevin Pouget
2013-01-15 19:02 ` Tom Tromey
2013-01-20 15:13 ` Matt Rice
2013-01-20 15:29 ` Robert Dewar [this message]
2013-01-20 15:39 ` shawn wilson
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=50FC0D53.7020403@adacore.com \
--to=dewar@adacore.com \
--cc=gdb@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=ratmice@gmail.com \
--cc=suryakiran.gullapalli@gmail.com \
--cc=tromey@redhat.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