Hi, My thinking about this arises from the fact that there is a person on one of the lists that I read who puts a semicolon after his name. Of course, this confuses the regex in notmuch-search-process-filter, which expects that the first semicolon in the string representing a thread is after all the authors.
I first thought of changing the regex so that it looked for the last semicolon in the string or something like that, but that would just move the problem. (Semicolons are probably more frequent in subject lines than in author names.) So it seems to me that what is needed is for notmuch and emacs to talk with each other in a format that is unambiguously parseable. Since notmuch search already has the option of outputting to JSON, that seems like a natural fit. Emacs has an existing JSON parser, <http://cvs.savannah.gnu.org/viewvc/*checkout*/emacs/lisp/json.el?root=emacs>, but it doesn't appear that it is able to parse progressively, meaning that it wouldn't be able to display results as they come in from notmuch search if used as-is. My guess is that its parts could be hacked together to overcome this limitation though. Anyway, if others think this is a good idea, I'm willing to do the coding. Cheers, Chris _______________________________________________ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch