From: David Symonds <dsymonds@gmail.com>
Date: Mon, 28 Jan 2008 23:11:05 GMT
Subject: Re: Configuration overrides via environment variable
Message-ID: <ee77f5c20801281511md7bdeeme383a140fdc854ec@mail.gmail.com>
In-Reply-To: <m3tzkx8smg.fsf@localhost.localdomain>

On Jan 29, 2008 9:58 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> Jan Hudec <bulb@ucw.cz> writes:
>
> > On Mon, Jan 28, 2008 at 12:08:10 +1100, David Symonds wrote:
> > >
> > > I'm using Git in some scripts, and wanted to get its colorised output
> > > even when it is not going to a tty. I don't want to permanently change
> > > ~/.gitconfig or the per-repo config; I just want to set color.status
> > > (and perhaps others) to "always" for a one-off run. I suppose I could
> > > munge the config files, storing the previous value and restoring it
> > > later, but that's messy.
>
> Cannot you just use --color option?

My version of Git (1.5.3.8) doesn't have a --color option for
git-status, and I can't find support for it in 'next', either. It
would be ideal if there was a --color option, though.


Dave.