how do the different frontends deal with displaying large queries?

diff --git a/91/cd002f29170306348b2fd051151ebd2671a842 b/91/cd002f29170306348b2fd051151ebd2671a842
new file mode 100644 (file)
index 0000000..dc92fc4
--- /dev/null
+++ b/91/cd002f29170306348b2fd051151ebd2671a842
@@ -0,0 +1,96 @@
+Return-Path: <eg@gaute.vetsj.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 arlo.cworth.org (Postfix) with ESMTP id 5C2FA6DE0B29\r
+ for <notmuch@notmuchmail.org>; Tue, 23 Feb 2016 22:50:02 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.355\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.355 tagged_above=-999 required=5 tests=[AWL=0.365,\r
+  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7,\r
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id ud7AlZZWNapN for <notmuch@notmuchmail.org>;\r
+ Tue, 23 Feb 2016 22:50:00 -0800 (PST)\r
+Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com\r
+ [209.85.215.53])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id E37C66DE0AC2\r
+ for <notmuch@notmuchmail.org>; Tue, 23 Feb 2016 22:49:59 -0800 (PST)\r
+Received: by mail-lf0-f53.google.com with SMTP id l143so5539658lfe.2\r
+ for <notmuch@notmuchmail.org>; Tue, 23 Feb 2016 22:49:59 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=gaute-vetsj-com.20150623.gappssmtp.com; s=20150623;\r
+ h=date:from:subject:to:references:in-reply-to:user-agent:message-id\r
+ :mime-version:content-type:content-transfer-encoding;\r
+ bh=jxP2qF/jsgZx/Ny1TPaSJ8q18tERg1D3/TPbkigDzyA=;\r
+ b=Gn1av5nrnXO6rj1rvRp90e4/5vpAwrTg1IM4/57tub6uEOvWWSaR0axlccm8Gj5zi+\r
+ 3uQ9V9tUowOL4YfwLaKl/xC66hstx7SCBgbDzyYuxuTE9CRsKJymfOA5Q7nVCgK/crcq\r
+ eSIV6kxuOKw4MM1SWL6A+5zVdggvqhoS//EJAHkj3waaNIShjHaEV/3fgfavhvONlH0A\r
+ 5UCN60kRlPQobCWaJYFZAoQEP0p/coq+hN70JOMLzy8BuDENoAuyPNxnwYnvgsLwgcb2\r
+ xc+ODJoq4unRuQmnYNw/7ZLZ5SulFjiiwEUzhBsJI0DeyPRAhLXijpZyWjmlp4HrxOem\r
+ Fjfw==\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=1e100.net; s=20130820;\r
+ h=x-gm-message-state:date:from:subject:to:references:in-reply-to\r
+ :user-agent:message-id:mime-version:content-type\r
+ :content-transfer-encoding;\r
+ bh=jxP2qF/jsgZx/Ny1TPaSJ8q18tERg1D3/TPbkigDzyA=;\r
+ b=Thj06n1G7x8rfYdSSq2CpT49Q7hyd40pXqBpqH0YXPCFZbmSQ6IPCDL0m2BQnoc0Yx\r
+ 6hb3ZNsn/rFgkXPkakELyBzs46u/nr8LiLspPGgEAG6xqhXGZ7ZgnFXcia/SMl6hxd6Z\r
+ peAl4bXyNSuCP4eYLg7x+bx9wyDTBODEkedNCw4UwxW2/S0yLTbSEN1CZLt/2uFh9R2b\r
+ mNbPL+DL8t7I+Ak4OdVq63mROZv8g+DX+DaF14hTWcrtwRf2ygs5TKSmNns8R7qS297Q\r
+ 3Dw9egLBdMWaq9/tQGnUl5iKFqpXW6E+i6S6CIw8oY/JTabcOYQcl6K4r43Y29B3fBLD\r
+ c1/Q==\r
+X-Gm-Message-State:\r
+ AG10YOSo5Tpf5Xosj+dAH14FogSr046Sr46ZPSg39UWeJktvp50G4bMLT/W7ZWAFBKU01Q==\r
+X-Received: by 10.25.160.140 with SMTP id j134mr14338366lfe.1.1456296596112;\r
+ Tue, 23 Feb 2016 22:49:56 -0800 (PST)\r
+Received: from localhost (c6878BF51.dhcp.as2116.net. [81.191.120.104])\r
+ by smtp.gmail.com with ESMTPSA id f196sm174340lfb.49.2016.02.23.22.49.54\r
+ for <notmuch@notmuchmail.org>\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Tue, 23 Feb 2016 22:49:54 -0800 (PST)\r
+Date: Wed, 24 Feb 2016 06:49:53 +0000\r
+From: Gaute Hope <eg@gaute.vetsj.com>\r
+Subject: how do the different frontends deal with displaying large queries?\r
+To: notmuch@notmuchmail.org\r
+References: \r
+In-Reply-To: \r
+User-Agent: astroid/v0.5-40-g7eeed380 (https://github.com/gauteh/astroid)\r
+Message-Id: <1456296267-astroid-0-gqidxpyulu-23762@strange>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8; format=flowed\r
+Content-Transfer-Encoding: quoted-printable\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 24 Feb 2016 06:50:02 -0000\r
+\r
+Hi,\r
+\r
+I am wondering how the different frontends deal with displaying large\r
+queries? Do you just display everything at the time? Or do you display a\r
+limited number and then show more on-demand?\r
+\r
+In the on-demand case; how do you get to the same position? Keeping a\r
+query object alive for long might make it invalid when the index is\r
+changed.\r
+\r
+Showing a limited number and restarting the query from the same position\r
+might miss threads if something in the first batch has been removed.\r
+\r
+Regards, Gaute\r
+\r
+=\r