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