git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC] send-email quote issues

From
Remi Lespinet <remi.lespinet@ensimag.grenoble-inp.fr>
Date
Jun 15, 2015, 13:03 UTC
Message-ID
<999870154.509851.1434373434414.JavaMail.zimbra@ensimag.grenoble-inp.fr>
In-Reply-To
<vpqmw011a22.fsf@anie.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes
> I would say that using parse_address_line is good for consistancy in Git 
> anyway. If the behavior of parse_address_line is broken on some 
> corner-cases, then it should be fixed anyway.

Ok, but I don't know what fixed means in these particular cases. Actually the problem when we have a quote in a name is: Is this a delimiter or is this an ascii char?

Currently the problem is solved by saying : it's an ascii char unless there is two quotes aroung all the name (modulo minor things). So if I write:

--to='"Jane, Kararina" Doe <jdoe@example.com>'

they are considered characters. Which means that this is different than:

--to='"Jane, Kararina Doe" <jdoe@example.com>'
Is this expected?
Previous: Matthieu MoyNext: Matthieu Moy
Message 3 of 5 in “[RFC] send-email quote issues”
  1. Remi LespinetJun 15, 2015
  2. Matthieu MoyJun 15, 2015
  3. Remi LespinetJun 15, 2015
  4. Matthieu MoyJun 15, 2015
  5. Remi LespinetJun 15, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.