The gitconfig syntax improperly highlights escaped double quotes. Escaping quotes is sometimes necessary (as in mergetool.cmd and others), but when it's done, the highlighting gets borked for the rest of the file.
With the changes in ca2c590 this is no longer the case. Also notice the properly highlighted "upstream" in both images (what the regex is specifically trying to capture).
Commit ca2c590 isn't necessarily relevant to this fix, but per http://git-scm.com/docs/git-config#FILES is an acceptable file path.
Don't highlight escaped double quotes.
Add git/config as possible file type.
Allowed per http://git-scm.com/docs/git-config#FILES.
Add proper escapes to unquoted string values
This fixes the issue in #16 where you may need to use a quote character without starting a quoted string context. Allowable escapes taken from http://git-scm.com/docs/git-config#FILES
Pulled 1ff4945, rather than a look-behind to detect invalid strings I added the proper escapes to unquoted string values in c2a675a. Thanks!