Re: [PATCH] config: use GIT_CONFIG in git config sequence

From: Matt Rogers <mattr94@gmail.com>
Date: Apr 26, 2020, 13:30 UTC
Message-ID: <CAOjrSZt7WJy1vv97Rw9MFJyTcB2Ehqq9BjGrXMtV95oB5p53SA@mail.gmail.com>
In-Reply-To: <ff9a63d4-80e4-8090-c85c-03fd3ab43c55@iee.email>

> Given the extra config environment settings, could/should the
> --show-scope (or complementary option) also show/clarify these
> environment variable settings?

I'm lukewarm either way on this one, I think it would be pretty trivial to write something that did this, so that only leaves the question of 'should' we do this, which I don't really have any particularly strong feelings about. What would this even ultimately look like? perhaps something like this for a command of `git config --show-scope`:

system var=option (currently ignored due to GIT_CONFIG_NOSYSTEM)

Which kind of begs the question of how many people set that variable and then forget that they set it? Although I can totally see why it would be nice to have some kind of config flag that's a big "Just show me everything that's going on option" which considering these variables would probably be a little bit more than the current next-best of `git config --list --show-scope --show-origin`. Again though, I'm not exactly sure how useful such an option would be.

-- 
Matthew Rogers