1 Return-Path: <cworth@cworth.org>
\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 DCA69431FC0;
\r
6 Fri, 27 Nov 2009 18:48:07 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id x9yGPHiBz6o3; Fri, 27 Nov 2009 18:48:07 -0800 (PST)
\r
11 Received: from cworth.org (localhost [127.0.0.1])
\r
12 by olra.theworths.org (Postfix) with ESMTP id 0460D431FAE;
\r
13 Fri, 27 Nov 2009 18:48:06 -0800 (PST)
\r
14 From: Carl Worth <cworth@cworth.org>
\r
15 To: Scott Robinson <scott@quadhome.com>, notmuch <notmuch@notmuchmail.org>
\r
16 In-Reply-To: <1259164514-sup-196@lisa>
\r
17 References: <1259164514-sup-196@lisa>
\r
18 Date: Fri, 27 Nov 2009 18:47:52 -0800
\r
19 Message-ID: <87zl67jrfr.fsf@yoom.home.cworth.org>
\r
21 Content-Type: text/plain; charset=us-ascii
\r
22 Subject: Re: [notmuch] Using notmuch from Ruby, Python, et al.
\r
23 X-BeenThere: notmuch@notmuchmail.org
\r
24 X-Mailman-Version: 2.1.12
\r
26 List-Id: "Use and development of the notmuch mail system."
\r
27 <notmuch.notmuchmail.org>
\r
28 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
29 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
30 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
31 List-Post: <mailto:notmuch@notmuchmail.org>
\r
32 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
33 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
34 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
35 X-List-Received-Date: Sat, 28 Nov 2009 02:48:08 -0000
\r
37 On Wed, 25 Nov 2009 08:16:54 -0800, Scott Robinson <scott@quadhome.com> wrote:
\r
38 > I'm hoping this thread will provide a guide for my efforts.
\r
40 > I'm writing a web frontend for notmuch in Ruby. But, the output from the
\r
41 > notmuch command-line is ambiguous. Therefore, I've started two branches
\r
42 > experimenting with different ways of providing hooks.
\r
44 Hi Scott, welcome to notmuch!
\r
46 A web frontend sounds very interesting, and I'll look forward to see
\r
47 what you come up with here.
\r
49 > Which of these approaches are likely to be pulled upstream?
\r
55 > I have modified the build to output a shared library. It's a small change
\r
56 > relying on libtool.
\r
58 We definitely want to have a shared library at some point. To some
\r
59 extent, publishing a shared library commits us to maintaining API/ABI
\r
60 for that library, and that's something I'm not willing to commit to
\r
61 at this point, (since we're still seeing a fair amount of churn in the
\r
64 But then again, we're also not even putting out a tar-file release yet
\r
65 either, so I think it's easy to say that we're not "publishing" anything
\r
66 yet and the API is all still subject to change.
\r
68 > However, the archives indicate Carl dislikes libtool?
\r
70 I've been maintaining a mainstream library (cairo) for several years
\r
71 that uses libtool in its build system. So I know what that's like and I
\r
72 definitely don't like it.
\r
74 I haven't yet tried maintaining a library without using libtool, but I'm
\r
75 optimistic that it will be much less painful, so that's what I'd like to
\r
80 > I added a --output=(text|json) option to "search" and "show." Then, emit json
\r
81 > results appropriately.
\r
83 > To accomplish this, I used the cJSON library sans parsing logic.
\r
85 > However, I saw discussion about providing a --format option?
\r
87 Obviously the exact name isn't that important and is easy to change. But
\r
88 yes, this kind of thing looks very interesting.
\r
90 > Q: Why are my replies five sentences or less?
\r
91 > A: http://five.sentenc.es/
\r
93 I guess I lose (or you do since you're the one receiving it). I count
\r
94 this as sentence number 13 in my reply. :-)
\r