From: Steven Cole <elenstev@mesatop.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: Daniel Serpell <daniel.serpell@gmail.com>,
GIT Mailing Lists <git@vger.kernel.org>
Subject: Re: [PATCH] Colorized git log
Date: Thu, 21 Apr 2005 19:04:18 -0600 [thread overview]
Message-ID: <200504211904.18283.elenstev@mesatop.com> (raw)
In-Reply-To: <20050422005452.GZ7443@pasky.ji.cz>
On Thursday 21 April 2005 06:54 pm, Petr Baudis wrote:
> Duh. And they say "Where possible terminfo is consulted to find the
> string to use." in their manual page. :/
>
> > gitlog.sh: 6d24d857fb6c2f7e810954adaca1990599906f07
> > --- a/gitlog.sh
> > +++ b/gitlog.sh
> > @@ -11,11 +11,11 @@
> >
> > if [ "$1" = "-c" ]; then
> > shift
> > - colheader=$(setterm -foreground green)
> > - colauthor=$(setterm -foreground cyan)
> > - colcommitter=$(setterm -foreground magenta)
> > - colsignoff=$(setterm -foreground yellow)
> > - coldefault=$(setterm -foreground default)
> > + colheader="$(tput setaf 2)"
> > + colauthor="$(tput setaf 6)"
> > + colcommitter="$(tput setaf 5)"
> > + colsignoff="$(tput setaf 3)"
> > + coldefault="$(tput op)"
> > else
> > colheader=
> > colauthor=
>
> Please at least stick the colors in comments after the assignment.
> Not everyone knows ANSI color codes off-hand (the last thing I've
> memorized were BIOS color codes in the distant DOS days).
>
I like the color idea, but since many people have their own idea
of what colors are appropriate, etc (I use a dark background, and
the magenta is painful), perhaps we could have a LOG_COLORS
file, similar in concept (but more readable) to the /etc/DIR_COLORS
file. Great work !
Steven
prev parent reply other threads:[~2005-04-22 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 21:12 Colorized git log Sean
2005-04-21 22:42 ` Petr Baudis
2005-04-22 0:46 ` [PATCH] " Daniel Serpell
2005-04-22 0:54 ` Petr Baudis
2005-04-22 1:04 ` Daniel Serpell
2005-04-22 1:04 ` Steven Cole [this message]
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=200504211904.18283.elenstev@mesatop.com \
--to=elenstev@mesatop.com \
--cc=daniel.serpell@gmail.com \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
/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).