From: Chris Gray <chrismgray@gmail.com>
To: notmuch@notmuchmail.org
Subject: [RFC] Use JSON in emacs interface
Date: Sun, 29 Apr 2012 10:22:01 -0600 [thread overview]
Message-ID: <87ty02v786.fsf@gmail.com> (raw)
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
next reply other threads:[~2012-04-29 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 16:22 Chris Gray [this message]
2012-04-29 18:17 ` [RFC] Use JSON in emacs interface Adam Wolfe Gordon
2012-04-29 20:11 ` Austin Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ty02v786.fsf@gmail.com \
--to=chrismgray@gmail.com \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).