git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Elijah Newren <newren@gmail.com>
Cc: Mike Ralphson <mike.ralphson@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] EasyGit (eg) 0.97
Date: Fri, 30 Jan 2009 15:29:17 -0500	[thread overview]
Message-ID: <20090130202917.GA3370@coredump.intra.peff.net> (raw)
In-Reply-To: <51419b2c0901301221n45cde1abw7a57a13bfa74b34@mail.gmail.com>

On Fri, Jan 30, 2009 at 01:21:00PM -0700, Elijah Newren wrote:

> Whenever I try to load the output in perl, git won't show the
> colorization.  I guess I could manually add it when I am printing the
> information, but it'd be nicer to just have git do the colorization
> despite the fact that its output is not a tty.  Is there an easy way
> to do that (without mucking with the user's config file)?
> 
> (It looks like eg status is also affected, for similar reasons.)

If you pass --color on the command line, it is equivalent to "color =
always" (whereas the default is "auto", which turns it on only if output
is to a tty).

So you would have to read color.diff yourself and then decide whether to
add --color.

Note that in general you are playing things a bit risky with these sorts
of outputs. You are calling porcelain (like log and status) and piping
it into your program. There's no guarantee that user config might not be
affecting the results of those programs.

But I think that is sort of the nature of "eg": to be a thin wrapper
around git. So maybe it is OK for your use.

-Peff

  reply	other threads:[~2009-01-30 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 16:42 [ANNOUNCE] EasyGit (eg) 0.97 Elijah Newren
2009-01-30 16:59 ` Mike Ralphson
2009-01-30 18:35   ` Elijah Newren
2009-01-30 19:47     ` Jeff King
2009-01-30 20:03       ` Jeff King
2009-01-30 20:22         ` Elijah Newren
2009-01-30 20:21       ` Elijah Newren
2009-01-30 20:29         ` Jeff King [this message]
2009-01-30 22:55           ` Elijah Newren
2009-01-31  7:25             ` 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=20090130202917.GA3370@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=mike.ralphson@gmail.com \
    --cc=newren@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 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).