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

From: Junio C Hamano <gitster@pobox.com>
Date: May 23, 2018, 08:58 UTC
Message-ID: <xmqqd0xmvjcq.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <alpine.LFD.2.21.1805230354270.16358@localhost.localdomain>

"Robert P. J. Day" <rpjday@crashcourse.ca> writes:

Show 9 quoted lines

>> If the documention does not make it clear, then we have
>> documentation bug ...
>
>   personally, i would add a short, really emphatic note at the top of
> "man git-config" pointing this out -- i wouldn't require people to
> read all the way down to "Syntax" to learn this. an example just like
> the one you provide above would be perfect, with an extra line
> pointing out that the documentation uses "camel case" for nothing more
> than readability.

Unfortunately, that line of thinking leads us to madness, as you are exhibiting the typical symptom of "my today's immediate itch is the most important one in the world"-itis. Tomorrow you would start saying that we must have a short, really emphatic note at the top that says that the second level name can even have spaces, and on the day after that, you would instead have a note that says that you cannot use an underscore in the name, and continuing that line of thought will lead us to fill the top part of the documentation with 47 different short and emphatic sentences. Let's not go there.