From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Colourise git-branch output
Date: Tue, 12 Dec 2006 11:03:29 +0000 [thread overview]
Message-ID: <200612121103.31110.andyparkins@gmail.com> (raw)
In-Reply-To: <7vpsapwhl2.fsf@assigned-by-dhcp.cox.net>
On Tuesday 2006 December 12 10:10, Junio C Hamano wrote:
> Even without red-green blindness issue, I think that makes
> sense. colored-diff uses green/red for added/deleted but that
I certainly don't have any objection. For me, the use of colour is not to
make things look pretty it's to give visual queues.
> is shown against the context in plain. A sane thing to do for
> branch listing would be to show the usual case (i.e. local) in
> plain and show the remote ones differently.
The only reason I picked red and green was to indicate "can be checked out"
and "cannot be checked out". However, when git eventually allows arbitrary
commits to be checked out that green/red, can/can't distinction will be
meaningless anyway.
> + "", /* LOCAL (normal) */
> + "\033[32m", /* CURRENT (green) */
In keeping with the "don't use green" idea - can I suggest just bold normal
for the CURRENT? That way there is the most minimal use of colour for the
default git-branch output, but still retaining a visual indicator.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-12-12 11:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 6:41 [PATCH] Colourise git-branch output Andy Parkins
2006-12-12 8:46 ` Johannes Sixt
2006-12-12 10:10 ` Junio C Hamano
2006-12-12 11:03 ` Andy Parkins [this message]
2006-12-12 18:43 ` Junio C Hamano
2006-12-12 18:43 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-12-11 22:10 Andy Parkins
2006-12-11 22:47 ` Junio C Hamano
2006-12-12 0:38 ` Sean
2006-12-12 1:11 ` Junio C Hamano
2006-12-12 1:24 ` Sean
2006-12-12 3:39 ` Linus Torvalds
2006-12-12 5:07 ` Junio C Hamano
2006-12-12 5:41 ` Linus Torvalds
2006-12-12 7:58 ` Junio C Hamano
2006-11-03 10:52 [PATCH] Add support to git-branch to show local and remote branches Andy Parkins
2006-11-03 12:06 ` [PATCH] Colourise git-branch output Andy Parkins
2006-11-03 19:25 ` Junio C Hamano
2006-11-03 23:05 ` Alex Riesen
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=200612121103.31110.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).