Re: should config options be treated as case-sensitive?

From: Junio C Hamano <gitster@pobox.com>
Date: May 23, 2018, 01:55 UTC
Message-ID: <xmqqo9h7w2y2.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <87h8mz99d2.fsf@evledraar.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

Show 5 quoted lines

> The issues you note about the docs using foo.barbaz instead of
> foo.barBaz should be fixed, but as noted in the "Syntax" section of
> "git-config" we already document that the config keys are all
> case-insensitive. We just like talking about them as foo.barBaz because
> it makes for easier reading.

The first and the last level of configuration variable names are case insensitive.

I said "first and last", as there are variables with 2-level and 3-level names. "foo.barBaz" is two-level and it is the same variable as "Foo.barbaz". "remote.origin.url" is three-level, and it is the same variable as "Remote.origin.URL", but it is not the same variable as "remote.ORIGIN.url".

If the documention does not make it clear, then we have documentation bug. As you said, I think we are OK in the sense that we do say a section or a variable name is icase and a subsection, if exist, is case sensitive, but there might be a better way to convey that fact without having the reader read the whole three paragraphs.