From: Joel Becker <Joel.Becker@oracle.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] git-status: colorize status output
Date: Sat, 5 Aug 2006 22:01:38 -0700 [thread overview]
Message-ID: <20060806050138.GN23246@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20060805031418.GA11102@coredump.intra.peff.net>
On Fri, Aug 04, 2006 at 11:14:19PM -0400, Jeff King wrote:
> The git-status output can sometimes be very verbose, making it difficult to
> quickly see whether your files are updated in the index. This adds 4 levels
> of colorizing to the status output:
> - general header (defaults to normal white)
> - updated but not committed (defaults to green)
> - changed but not updated (defaults to red)
> - untracked files (defaults to red)
Please do one of two things:
1) Add code to discover a terminal is white-on-black and use bright colors
or
2) Default this to off.
I like the idea of colors, but the colors most people use in
black-on-white terminals are invisible on my screen. colorls has the
same problem.
Joel
--
"What no boss of a programmer can ever understand is that a programmer
is working when he's staring out of the window"
- With apologies to Burton Rascoe
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2006-08-06 5:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 3:14 [PATCH] git-status: colorize status output Jeff King
2006-08-05 3:21 ` Jeff King
2006-08-05 8:16 ` Greg KH
2006-08-05 9:28 ` Junio C Hamano
2006-08-05 10:21 ` Jeff King
2006-08-05 10:44 ` Jeff King
2006-08-05 10:59 ` Matthias Lederhofer
2006-08-05 11:21 ` Junio C Hamano
2006-08-05 11:27 ` Junio C Hamano
2006-08-05 11:28 ` Matthias Lederhofer
2006-08-05 11:42 ` Junio C Hamano
2006-08-05 12:18 ` Matthias Lederhofer
2006-08-05 19:54 ` Jeff King
2006-08-05 20:31 ` Matthias Lederhofer
2006-08-05 19:51 ` Jeff King
2006-08-07 17:12 ` Sam Ravnborg
2006-08-05 19:45 ` Jeff King
2006-08-05 20:27 ` Matthias Lederhofer
2006-08-05 23:42 ` Jeff King
2006-08-06 5:01 ` Joel Becker [this message]
2006-08-06 6:16 ` Jeff King
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=20060806050138.GN23246@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=peff@peff.net \
/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).