From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Seth Bollinger <seth.boll@gmail.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2] bitbake: Colorize knotty interactive console output
Date: Tue, 13 Nov 2012 14:23:43 +0000 [thread overview]
Message-ID: <1352816623.24487.128.camel@ted> (raw)
In-Reply-To: <CA+JN8xNzAvDdt4bgS=z536YciYVAvZGE2+Z=qQa1XP4HCE8=gg@mail.gmail.com>
On Sun, 2012-11-11 at 09:17 -0600, Seth Bollinger wrote:
> Add bold color output to log level name and standard color output to
> log msg
> when bitbake is run from an iteractive console. Color output is only
> enabled
> if the terminal supports color.
>
> Signed-off-by: Seth Bollinger <seth.boll@gmail.com>
> ---
> bitbake/lib/bb/msg.py | 40
> ++++++++++++++++++++++++++++++++++++++++
> bitbake/lib/bb/ui/knotty.py | 6 +++++-
> 2 files changed, 45 insertions(+), 1 deletions(-)
I love the idea. I tried testing it and realised that it doesn't work in
my black text on a white background terminals though, the result of the
patch was unreadable :(
Cheers,
Richard
next prev parent reply other threads:[~2012-11-13 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 15:17 [PATCH v2] bitbake: Colorize knotty interactive console output Seth Bollinger
2012-11-11 22:54 ` Chris Larson
2012-11-12 2:02 ` Seth Bollinger
2012-11-12 2:24 ` Chris Larson
2012-11-13 14:23 ` Richard Purdie [this message]
2012-11-13 14:45 ` Seth Bollinger
2012-11-13 15:22 ` Richard Purdie
2012-11-13 22:36 ` Jason Wessel
2012-11-14 13:18 ` Seth Bollinger
2012-11-14 13:22 ` Richard Purdie
2012-11-14 14:43 ` Seth Bollinger
2012-11-14 23:26 ` Richard Purdie
[not found] ` <CA+JN8xN-vkLxtd+J4BZoQ39xs3Yujh-J=CQ8q+T1k0r-t-bpzA@mail.gmail.com>
2012-11-16 14:45 ` Seth Bollinger
2012-11-22 3:36 ` Robert Yang
2012-11-25 21:37 ` Richard Purdie
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=1352816623.24487.128.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=seth.boll@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.