1 Return-Path: <scott@quadhome.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id DB2E1431FBD
\r
6 for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 13:44:04 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
\r
12 tests=[BAYES_50=0.001] autolearn=ham
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id 1xab5LpA754O for <notmuch@notmuchmail.org>;
\r
16 Mon, 1 Feb 2010 13:44:04 -0800 (PST)
\r
17 Received: from julia.quadhome.com (quadhome.xen.prgmr.com [68.68.99.250])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 342D8431FAE
\r
19 for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 13:44:04 -0800 (PST)
\r
20 Received: from elise.quadhome.com (168.101.148.190.dsl.intelnet.net.gt
\r
22 by julia.quadhome.com (Postfix) with ESMTPSA id 0A9D95FBC2
\r
23 for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 21:44:02 +0000 (UTC)
\r
24 Content-Type: text/plain; charset=UTF-8
\r
25 From: Scott Robinson <scott@quadhome.com>
\r
26 To: notmuch <notmuch@notmuchmail.org>
\r
27 In-reply-to: <fceba468c7dc42532528f699e51879ab.squirrel@webmail.sspaeth.de>
\r
28 References: <87eil4ygar.fsf@servo.finestructure.net>
\r
29 <fceba468c7dc42532528f699e51879ab.squirrel@webmail.sspaeth.de>
\r
30 Date: Mon, 01 Feb 2010 15:43:59 -0600
\r
31 Message-Id: <1265060613-sup-6646@elise>
\r
32 User-Agent: Sup/0.10.2
\r
33 Content-Transfer-Encoding: 8bit
\r
34 Subject: Re: [notmuch] Request for high-priority improvements to notmuch
\r
35 X-BeenThere: notmuch@notmuchmail.org
\r
36 X-Mailman-Version: 2.1.13
\r
38 List-Id: "Use and development of the notmuch mail system."
\r
39 <notmuch.notmuchmail.org>
\r
40 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
41 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
42 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
43 List-Post: <mailto:notmuch@notmuchmail.org>
\r
44 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
45 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
47 X-List-Received-Date: Mon, 01 Feb 2010 21:44:05 -0000
\r
49 Excerpts from sebastian's message of Mon Feb 01 14:29:44 -0600 2010:
\r
51 > > JSON output for "notmuch search/show" with ability to filter output fields
\r
52 > > "search" --> "search --output=thread_id,date,number,author,subject,tags"
\r
53 > > "show" --> "search
\r
54 > > --output=message_id,tags,path,header,body,attachments"
\r
56 > YES PLEASE :-). notmuch seems designed to work in an ecosystem of
\r
57 > surrounding scripts, feeding data in and out. But we are all currently
\r
58 > limited to regexes for that. And heck, I hard a hard time understanding
\r
59 > why all hell broke out until I found that i had added a tag containing
\r
60 > parentheses which made my regex fail. :-). XML, JSON, any structured
\r
61 > output would be nice.
\r
63 > And as for filtering: YES, PLEASE :-). notmuchsync and many other 3rd
\r
64 > party apps would love that. As father of notmuchsync, I can tell you my
\r
65 > little script hickups very badly when slurping in 200k mails (including
\r
66 > text bodies) just to find out the maildir tags of those mails.
\r
69 There's been a JSON patch waiting for a month now.
\r