Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 462CD6DE0275 for ; Wed, 24 Feb 2016 09:49:03 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.036 X-Spam-Level: X-Spam-Status: No, score=-0.036 tagged_above=-999 required=5 tests=[AWL=-0.025, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IzuzKTrPaXif for ; Wed, 24 Feb 2016 09:49:01 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id ED7A76DE00DF for ; Wed, 24 Feb 2016 09:49:00 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aYdZC-0008Fb-28; Wed, 24 Feb 2016 12:49:38 -0500 Received: (nullmailer pid 14826 invoked by uid 1000); Wed, 24 Feb 2016 17:48:54 -0000 From: David Bremner To: Gaute Hope , notmuch@notmuchmail.org Subject: Re: how do the different frontends deal with displaying large queries? In-Reply-To: <1456296267-astroid-0-gqidxpyulu-23762@strange> References: <1456296267-astroid-0-gqidxpyulu-23762@strange> User-Agent: Notmuch/0.21+5~gca076ce (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Wed, 24 Feb 2016 13:48:54 -0400 Message-ID: <87ziuqj8xl.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Wed, 24 Feb 2016 17:49:03 -0000 Gaute Hope writes: > Hi, > > I am wondering how the different frontends deal with displaying large > queries? Do you just display everything at the time? Or do you display a > limited number and then show more on-demand? > I only know the emacs front end, and I suspect the answer won't help you much. We start filling an emacs buffer asynchronously with the results, and display the top of the buffer with the first results. Results are appended to the end of the buffer, typically much faster than the user can scroll. d