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

"Robert P. J. Day" writes: >> 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 > > fair enough, point taken. FWIW, everybody suffers

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

On Wed, 23 May 2018, Junio C Hamano wrote: > "Robert P. J. Day" writes: > > >> 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

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

"Robert P. J. Day" writes: >> 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

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

On Wed, 23 May 2018, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: > > > 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

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

Ævar Arnfjörð Bjarmason writes: > 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

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

On Tue, 22 May 2018, Ævar Arnfjörð Bjarmason wrote: > > On Tue, May 22 2018, Robert P. J. Day wrote: > > > in my wanderings, more oddities, such as this: > > > > $ grep -ir blankboundary * > > builtin/blame.c:if (!strcmp(var, "blame.blankboundary")) { > >

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

On Tue, May 22 2018, Robert P. J. Day wrote: > in my wanderings, more oddities, such as this: > > $ grep -ir blankboundary * > builtin/blame.c: if (!strcmp(var, "blame.blankboundary")) { > Documentation/config.txt:blame.blankBoundary:: > Documentation/blame-options.txt: be controlled

should config options be treated as case-sensitive?

in my wanderings, more oddities, such as this: $ grep -ir blankboundary * builtin/blame.c:if (!strcmp(var, "blame.blankboundary")) { Documentation/config.txt:blame.blankBoundary:: Documentation/blame-options.txt:be controlled via the `blame.blankboundary` config option.