From: Jeff King <peff@peff.net>
To: Daniel Villeneuve <daniel2villeneuve@videotron.ca>
Cc: git@vger.kernel.org
Subject: Re: git -c var=val not taken into account by git config?
Date: Tue, 8 May 2012 05:16:06 -0400 [thread overview]
Message-ID: <20120508091606.GB31286@sigill.intra.peff.net> (raw)
In-Reply-To: <4FA857E3.5030609@videotron.ca>
On Mon, May 07, 2012 at 07:16:51PM -0400, Daniel Villeneuve wrote:
> Testing color configuration via scripting, I tried the following command:
>
> git -c color.diff=always config --get-colorbool diff false
>
> on a repository with color.diff=auto.
>
> I'd expect "true" as output, but got "false". "git diff" works as
> expected though. Is this an exception for "git config"?
I think you meant "--get-colorbool color.diff"; the fact that you are
getting a colorbool does not automatically place the name inside the
color.* section.
With that change, it seems to work as expected.
-Peff
next prev parent reply other threads:[~2012-05-08 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 23:16 git -c var=val not taken into account by git config? Daniel Villeneuve
2012-05-08 9:16 ` Jeff King [this message]
2012-05-08 12:56 ` Daniel Villeneuve
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=20120508091606.GB31286@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=daniel2villeneuve@videotron.ca \
--cc=git@vger.kernel.org \
/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).