From: Tom Tromey <tromey@redhat.com>
To: Andrew Sutherland <sombrero@alum.mit.edu>
Cc: archer@sourceware.org
Subject: Re: [python] how best to support colorized output? (with example colorized backtrace)
Date: Fri, 27 Mar 2009 00:19:00 -0000 [thread overview]
Message-ID: <m3hc1fvmvo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <gqgvh5$3iq$1@ger.gmane.org> (Andrew Sutherland's message of "Thu\, 26 Mar 2009 15\:27\:48 -0700")
>>>>> "Andrew" == Andrew Sutherland <sombrero@alum.mit.edu> writes:
Andrew> http://www.visophyte.org/blog/2009/03/04/gaudily-colorized-gdb-backtraces-woo/
Cool!
Andrew> Thiago dropped by and commented, suggesting I post about it here.
Nice outreach, thanks Thiago.
Andrew> While my solution was never intended to make it upstream (and should
Andrew> not), I'd be interesting in finding out how colorized output could be
Andrew> implemented that could be integrated.
I think the only thing I would suggest would be to use the existing
filtering backtrace, and just reimplement colorization as a filter.
If that's not possible (I didn't dig into the details too much), let's
modify the existing Python backtrace command to make it possible :-)
Tom
next prev parent reply other threads:[~2009-03-27 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 22:35 Andrew Sutherland
2009-03-27 0:19 ` Tom Tromey [this message]
2009-03-27 0:44 ` Andrew Sutherland
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=m3hc1fvmvo.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=sombrero@alum.mit.edu \
/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).