git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Configuration overrides via environment variable

From
David Symonds <dsymonds@gmail.com>
Date
Jan 28, 2008, 23:11 UTC
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:
Show 12 quoted lines
> 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.
Previous: Jakub Narebski
Message 4 of 4 in “Configuration overrides via environment variable”
  1. David SymondsJan 28, 2008
  2. Jan HudecJan 28, 2008
  3. Jakub NarebskiJan 28, 2008
  4. David SymondsJan 28, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.