public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paul Varner" <fuzzyray@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:gentoolkit commit in: pym/gentoolkit/
Date: Wed, 16 May 2012 21:18:15 +0000 (UTC)	[thread overview]
Message-ID: <1337202723.df024db3a4573d89d11a59d0c05be7d4f3d7e143.fuzzyray@gentoo> (raw)

commit:     df024db3a4573d89d11a59d0c05be7d4f3d7e143
Author:     Paul Varner <fuzzyray <AT> gentoo <DOT> org>
AuthorDate: Wed May 16 21:12:03 2012 +0000
Commit:     Paul Varner <fuzzyray <AT> gentoo <DOT> org>
CommitDate: Wed May 16 21:12:03 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/gentoolkit.git;a=commit;h=df024db3

Make colors for useflags be the same as portage.

The current colors are the opposite of how portage uses the colors.
This just switches them so portage and equery show the same color for
the same meaning, Red is a set useflag and blue is an unset useflag.

Note: This ignores any user defined colormaps in portage.

---
 pym/gentoolkit/pprinter.py |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/pym/gentoolkit/pprinter.py b/pym/gentoolkit/pprinter.py
index d9f0375..7d8dc2c 100644
--- a/pym/gentoolkit/pprinter.py
+++ b/pym/gentoolkit/pprinter.py
@@ -116,7 +116,7 @@ def subsection(string):
 
 def useflag(string, enabled=True):
 	"""Returns a USE flag string."""
-	return output.blue(string) if enabled else output.red(string)
+	return output.red(string) if enabled else output.blue(string)
 
 def keyword(string, stable=True, hard_masked=False):
 	"""Returns a keyword string."""



             reply	other threads:[~2012-05-16 21:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 21:18 Paul Varner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-02 22:10 [gentoo-commits] proj/gentoolkit:gentoolkit commit in: pym/gentoolkit/ Paul Varner
2014-02-22 19:28 Brian Dolbec
2013-03-12 16:06 Mike Frysinger
2013-01-04 22:23 Paul Varner
2012-12-30 20:25 Brian Dolbec
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-11-13 20:40 Paul Varner
2012-10-09 21:35 Paul Varner
2012-08-01  3:34 Brian Dolbec
2012-07-24 17:18 Paul Varner
2012-03-02  0:01 Brian Dolbec
2011-12-23  6:05 Brian Dolbec
2011-07-16  4:04 Paul Varner
2011-07-16  3:21 Paul Varner
2011-07-15 20:02 Paul Varner
2011-05-23  3:45 Brian Dolbec
2011-05-20  5:54 Brian Dolbec
2011-05-18 21:18 Brian Dolbec
2011-04-18 18:28 Paul Varner
2011-03-31 21:53 Paul Varner
2011-02-23  9:10 Brian Dolbec

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=1337202723.df024db3a4573d89d11a59d0c05be7d4f3d7e143.fuzzyray@gentoo \
    --to=fuzzyray@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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