[RFC] Use JSON in emacs interface

diff --git a/fd/de90c0d484f9100106ed03547a6295ce1a473f b/fd/de90c0d484f9100106ed03547a6295ce1a473f
new file mode 100644 (file)
index 0000000..278939c
--- /dev/null
+++ b/fd/de90c0d484f9100106ed03547a6295ce1a473f
@@ -0,0 +1,91 @@
+Return-Path: <chrismgray@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 1F85C431FAF\r
+       for <notmuch@notmuchmail.org>; Sun, 29 Apr 2012 09:22:10 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id WlLXnwiijnc8 for <notmuch@notmuchmail.org>;\r
+       Sun, 29 Apr 2012 09:22:09 -0700 (PDT)\r
+Received: from mail-pb0-f53.google.com (mail-pb0-f53.google.com\r
+       [209.85.160.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 71F74431FAE\r
+       for <notmuch@notmuchmail.org>; Sun, 29 Apr 2012 09:22:09 -0700 (PDT)\r
+Received: by pbbrr4 with SMTP id rr4so3281086pbb.26\r
+       for <notmuch@notmuchmail.org>; Sun, 29 Apr 2012 09:22:07 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=from:to:subject:user-agent:date:message-id:mime-version\r
+       :content-type; bh=lD8EshTNjlY30kn/YFHqi/KrnTaY8yjx4s/dOkem/po=;\r
+       b=d7HZ8XK0veqhx9YoGzkAbpElalBWJR5KTrzNQLubwODzrr/cR8wO5VPnse1EVnMkrE\r
+       HIxeJsIqXAX/Onsb64fDnWewWFTLDRTC00Cj1Jf0hXHyGAZriio4CKB87rXVcBirHxY5\r
+       dJaaKDXJ0g4kXqQaaeXNMe0G2JP01hC/PbKfK68z+/Ny3ReEDvT0f+U/cq7qFwT3RxTS\r
+       7/ThH487OR8UXxO/pDw5I8kvNpG5sjH7QAIk66dBpQnb6vzwox6jG8q/XFHZaNupE7T1\r
+       LIyVGzaNvV3dmfhK/XDhuGhDNti+J/9b2ebmHEgLlNRyexPyhq+AmAjEVnEQUnjcdPGZ\r
+       YX9A==\r
+Received: by 10.68.132.201 with SMTP id ow9mr1649305pbb.160.1335716527466;\r
+       Sun, 29 Apr 2012 09:22:07 -0700 (PDT)\r
+Received: from driftwood (S0106001f333bc36d.cg.shawcable.net. [68.144.78.164])\r
+       by mx.google.com with ESMTPS id\r
+       i1sm13216604pbv.49.2012.04.29.09.22.05\r
+       (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Sun, 29 Apr 2012 09:22:06 -0700 (PDT)\r
+From: Chris Gray <chrismgray@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: [RFC] Use JSON in emacs interface\r
+User-Agent: Notmuch/0.12+91~gb6d1eb9 (http://notmuchmail.org) Emacs/24.0.93.1\r
+       (i486-pc-linux-gnu)\r
+Date: Sun, 29 Apr 2012 10:22:01 -0600\r
+Message-ID: <87ty02v786.fsf@gmail.com>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 29 Apr 2012 16:22:10 -0000\r
+\r
+Hi,\r
+\r
+My thinking about this arises from the fact that there is a person on\r
+one of the lists that I read who puts a semicolon after his name.  Of\r
+course, this confuses the regex in notmuch-search-process-filter, which\r
+expects that the first semicolon in the string representing a thread is\r
+after all the authors.\r
+\r
+I first thought of changing the regex so that it looked for the last\r
+semicolon in the string or something like that, but that would just move\r
+the problem.  (Semicolons are probably more frequent in subject lines\r
+than in author names.)  So it seems to me that what is needed is for\r
+notmuch and emacs to talk with each other in a format that is\r
+unambiguously parseable.  Since notmuch search already has the option of\r
+outputting to JSON, that seems like a natural fit.\r
+\r
+Emacs has an existing JSON parser,\r
+<http://cvs.savannah.gnu.org/viewvc/*checkout*/emacs/lisp/json.el?root=emacs>,\r
+but it doesn't appear that it is able to parse progressively, meaning\r
+that it wouldn't be able to display results as they come in from notmuch\r
+search if used as-is.  My guess is that its parts could be hacked\r
+together to overcome this limitation though.\r
+\r
+Anyway, if others think this is a good idea, I'm willing to do the\r
+coding.\r
+\r
+Cheers,\r
+Chris\r