From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 12065429E24 for ; Fri, 28 Jan 2011 14:02:52 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.99 X-Spam-Level: X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, T_MIME_NO_TEXT=0.01] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdEBs0ZoasYy; Fri, 28 Jan 2011 14:02:51 -0800 (PST) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id B5F5B431FB6; Fri, 28 Jan 2011 14:02:50 -0800 (PST) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 30C832540DF; Sat, 29 Jan 2011 06:27:42 +1000 (EST) From: Carl Worth To: Christophe-Marie Duquesne , Sebastian Spaeth Subject: Re: About the json output and the number of results shown. In-Reply-To: References: <8762ttf5wy.fsf@SSpaeth.de> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1 (i486-pc-linux-gnu) Date: Sat, 29 Jan 2011 06:27:42 +1000 Message-ID: <87sjwcn58h.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Cc: notmuch@notmuchmail.org X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jan 2011 22:02:52 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Thu, 13 Jan 2011 19:46:29 +0100, Christophe-Marie Duquesne wrote: > I've had a look to the python libnotmuch documentation. My problem > with this API is that, unless I did not read it correctly, if I use > one of its functions in a threaded fashion, I still have to wait for > this function to finish until I get results. The search function should return very quickly (ore pretty close to that anyway). It's only when you start iterating through the results that there's a lot of time being spent in the library functions. > When using the command > line tool, I can process the text as it gets printed on stdout, and I > have data to show to the user even though notmuch has not finished to > output it... This functionality of the command-line tool is implemented with the same library functions you would call. So you should get exactly the same behavior that you want by calling the library directly. Please let us know if that's not the case. =2DCarl =2D-=20 carl.d.worth@intel.com --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFNQya+6JDdNq8qSWgRAp7QAKClbv16DIpsZmcAXH2pH2tl7RqR/QCeImP9 PXHRxDWBFXsuEkNKL43CJDE= =nuUV -----END PGP SIGNATURE----- --=-=-=--