Re: git silently ignores include directive with single quotes
- From
- Stas Bekman <stas@stason.org>
- Date
- Sep 8, 2018, 19:53 UTC
- Message-ID
- <a76c94c6-9fd7-4ed0-be2d-6fc1d021f476@stason.org>
- In-Reply-To
- <CAN0heSroxfcwiJaVgGFTweq=XKAgGsR-E6SeOgsG4m0rzK4dHQ@mail.gmail.com>
On 2018-09-08 12:30 PM, Martin Ågren wrote:
Show 5 quoted lines
> Hi Stas > > On Sat, 8 Sep 2018 at 21:00, Stas Bekman <stas@stason.org> wrote: >> [include] >> path = '../.gitconfig'
> Actually, there is a test explicitly testing that 'missing include files > are ignored'. I couldn't find a motivation for this in 9b25a0b52e > (config: add include directive, 2012-02-06).
And also to stress out, that the file is not missing. At least in the world of unix, in particular its many shells, - command line arguments "xyz", 'xyz', xyz are often deemed to be the same if there are no spaces in the word. So that's why it took us a lot of trial and error to even consider the quotes in '../.gitconfig' as a problem. While git deems it different, to me:
path = '../.gitconfig'
path = "../.gitconfig"
path = ../.gitconfigappear to be the "same". So git needs to have a way to say otherwise.
I realize I am going back to the issue of quoting here, after suggesting to ignore it. So to clarify I'm bringing it up only in the context of wanting git to tell the user what it wants, and not necessarily asking to support all the possible ways one could quote a filepath.
-- ________________________________________________ Stas Bekman <'))))>< <'))))>< https://stasosphere.com https://chestofbooks.com https://experientialsexlab.com https://stason.org https://stasosphere.com/experience-life/my-books