Re: [PATCH 1/1] config: allow user to know scope of config options

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 21, 2019, 23:47 UTC
Message-ID: <xmqqpngh6y1j.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CAOjrSZvkT3TZwEvvnhRBVcuivhy46n8p9sV+3wZdvD=5f_cuRQ@mail.gmail.com>

Matt Rogers <mattr94@gmail.com> writes:

> And that origin and scope correlate, but aren't necessarily
> one-for-one.

Yes, exactly. When I see "orthogonal", I expect the word describes things that do not correlate.

I can see values in the option that gives scope but not path in order to write scripts that limits var-value pairs to be used (e.g. "I do not want to be affected by the per-repository values", "I do not trust settings that comes system-wide"). I also can see values in the option that gives only path when debugging the configuration file.

I briefly wondered, for the purpose of such "I do want to see only those settings coming from these scopes" script, it may make more sense to have the command _filter_ the var-value pairs, instead of showing all of them with label, but that feature always exists ;-)