Incorrect handling of backslashes in Git configuration#45
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Steps to reproduce the issue:
Now if you try to read this value using a regular (non Python)
git config, Git complains that the configuration file is invalid:Indeed, if you open
.git/configyou can see that the value is written as:While the
git-configconfiguration states that:That is, the backslashes are not escaped in the configuration file.
This also causes issues while reading, because values are not un-escaped.
I provided a sample fixing commit: changes are simple but I couldn't test it (I have no access to any Python installation right now and did the change online).