Re: About the json output and the number of results shown.

diff --git a/ac/b7b0e20f752a733f0f5646292e68b3b199a27a b/ac/b7b0e20f752a733f0f5646292e68b3b199a27a
new file mode 100644 (file)
index 0000000..6ba1a86
--- /dev/null
+++ b/ac/b7b0e20f752a733f0f5646292e68b3b199a27a
@@ -0,0 +1,74 @@
+Return-Path: <chm.duquesne@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 3F4D0429E35\r
+       for <notmuch@notmuchmail.org>; Thu, 13 Jan 2011 10:46:57 -0800 (PST)\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 8QzBCtX-C4Td for <notmuch@notmuchmail.org>;\r
+       Thu, 13 Jan 2011 10:46:57 -0800 (PST)\r
+Received: from mail-ww0-f45.google.com (mail-ww0-f45.google.com\r
+ [74.125.82.45])       by olra.theworths.org (Postfix) with ESMTP id B500B429E34       for\r
+ <notmuch@notmuchmail.org>; Thu, 13 Jan 2011 10:46:56 -0800 (PST)\r
+Received: by wwb29 with SMTP id 29so2010959wwb.2\r
+       for <notmuch@notmuchmail.org>; Thu, 13 Jan 2011 10:46:49 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;\r
+       h=domainkey-signature:mime-version:in-reply-to:references:from:date\r
+       :message-id:subject:to:cc:content-type;\r
+       bh=gD+hIPz+etg3h0IYs9POmFVwknpDlVkCuaD78W2TQhA=;\r
+       b=TtWChm1NaiwE0HyJFp8i1Uu6uuCtvpIjk/aXovuJjKfNRDoEinC/bbALkk/meUOn8H\r
+       kzIV+XgA0NTmPtUkDl0VNSYyS/zm5YzGmsqhNWnbtZALQkJekwZG/XOHZ+5kzWx/OC5F\r
+       HxPmWRyBdVHRNq8RPEQEvEf12pfM5Us1yE50E=\r
+DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;\r
+       h=mime-version:in-reply-to:references:from:date:message-id:subject:to\r
+       :cc:content-type;\r
+       b=YxJEQKkI7qtUXn21JZeunmVnSqaekZqpPHiRxzNkJdKCLawFe4aBWo0bok00KTmVPq\r
+       RdTQl5U9ecFx8FbJJZfq0cJhqNiTrSdfl0Qi5w8Q4GWod9qeFcqgACU97DCxqLwI40do\r
+       hsSMuCCjztw6stOuBh+188Ai3WcVaAa8MiqBI=\r
+Received: by 10.227.141.131 with SMTP id m3mr2682194wbu.125.1294944409389;\r
+       Thu, 13 Jan 2011 10:46:49 -0800 (PST)\r
+MIME-Version: 1.0\r
+Received: by 10.227.143.206 with HTTP; Thu, 13 Jan 2011 10:46:29 -0800 (PST)\r
+In-Reply-To: <8762ttf5wy.fsf@SSpaeth.de>\r
+References: <AANLkTi=Mzu9bu3y0RKB5YZUpZOT9qujXgxtpB-8Bvk=2@mail.gmail.com>\r
+       <8762ttf5wy.fsf@SSpaeth.de>\r
+From: Christophe-Marie Duquesne <chm.duquesne@gmail.com>\r
+Date: Thu, 13 Jan 2011 19:46:29 +0100\r
+Message-ID: <AANLkTimYDZaHBxNxkJHfs+4Ww73_+7oEqW+bOexskJjU@mail.gmail.com>\r
+Subject: Re: About the json output and the number of results shown.\r
+To: Sebastian Spaeth <Sebastian@sspaeth.de>\r
+Content-Type: text/plain; charset=UTF-8\r
+Cc: notmuch@notmuchmail.org\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: Thu, 13 Jan 2011 18:46:57 -0000\r
+\r
+> Alternatively, you could use the python bindings to libnotmuch and call\r
+> the functions directly. You could do that in a unthreaded or threaded\r
+> fashion...\r
+\r
+I've had a look to the python libnotmuch documentation. My problem\r
+with this API is that, unless I did not read it correctly, if I use\r
+one of its functions in a threaded fashion, I still have to wait for\r
+this function to finish until I get results. When using the command\r
+line tool, I can process the text as it gets printed on stdout, and I\r
+have data to show to the user even though notmuch has not finished to\r
+output it...\r