René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"GitConfigParser misparses quotes in options","articleBody":"My `~/.gitconfig` starts like this:\r\n\r\n```\r\n[user]\r\n        name = \"Colin Watson\"\r\n        email = \"cjwatson@debian.org\"\r\n```\r\n\r\nIt's been like that for a long time, so I don't remember whether an old version of `git config` wrote it like that, or whether I put it there by hand.  Anyway, `git` itself has always been fine with this.  The relevant part of git-config(1) says:\r\n\r\n\u003e A line that defines a value can be continued to the next line by ending it with a \\; the backslash and the end-of-line are stripped. Leading whitespaces after name =, the remainder of the line after the first comment character # or ;, and trailing whitespaces of the line are discarded unless they are enclosed in double quotes. Internal whitespaces within the value are retained verbatim.\r\n\u003e \r\n\u003e Inside double quotes, double quote \" and backslash \\ characters must be escaped: use \\\" for \" and \\\\ for \\.\r\n\u003e \r\n\u003e The following escape sequences (beside \\\" and \\\\) are recognized: \\n for newline character (NL), \\t for horizontal tabulation (HT, TAB) and \\b for backspace (BS). Other char escape sequences (including octal escape sequences) are invalid.\r\n\r\nBut when I create a commit using `IndexFile.commit()`, I get this in the commit metadata, which I'm pretty sure is malformed:\r\n\r\n`Author: \"Colin Watson\" \u003c\"cjwatson@debian.org\"\u003e`\r\n\r\nI think `GitConfigParser` should match the parsing rules that `git config` follows.","author":{"url":"https://github.com/cjwatson","@type":"Person","name":"cjwatson"},"datePublished":"2024-05-31T14:51:49.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1923/GitPython/issues/1923"}