Re: how do the different frontends deal with displaying large queries?

diff --git a/a0/93cac65df657f292ed704ab74370e52c0b982b b/a0/93cac65df657f292ed704ab74370e52c0b982b
new file mode 100644 (file)
index 0000000..3d2f30b
--- /dev/null
+++ b/a0/93cac65df657f292ed704ab74370e52c0b982b
@@ -0,0 +1,116 @@
+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 B813F6DE17EE\r
+ for <notmuch@notmuchmail.org>; Fri, 26 Feb 2016 03:50:48 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.448\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.448 tagged_above=-999 required=5 tests=[AWL=0.272,\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 28_P9IDddCSV for <notmuch@notmuchmail.org>;\r
+ Fri, 26 Feb 2016 03:50:46 -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 1458B6DE0BF6\r
+ for <notmuch@notmuchmail.org>; Fri, 26 Feb 2016 03:50:45 -0800 (PST)\r
+Received: by mail-lf0-f53.google.com with SMTP id m1so51928399lfg.0\r
+ for <notmuch@notmuchmail.org>; Fri, 26 Feb 2016 03:50:45 -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-transfer-encoding;\r
+ bh=PYSMaeeFe8i1SzU/yZqXaYUErh4YI6HCHYLp41fuReo=;\r
+ b=UCyBkBhk1VisfepcCmx+P8RyduMfv59QNFuk7zO4udrTXy+ZS7OLE17Axj7vXbtNxh\r
+ ZoVtnlsmhaU1JHUKHbe6LMiG149tfGzAGpR6IWATM//wlgiVJe1T87i4xMc+Vy+L9c7O\r
+ CAH8kAm4BEGeI4272eOt0lVJeuo6Y9/IzCehkJclwI253lgyawlKdySJqvRCdlBPM9BR\r
+ nJLu8NoNSOXSCfglx/pPIkMdix38sSfzp9h6zUk3Gn5LfM8YGTTXKPAmJ+uomkEkKnGY\r
+ kfLHjqfT0Gw6FUKRrXM3ZGChbXF40T8eXURnBTNdDMUNtVjEZJB90kslFgueeYPH7xVm\r
+ aoCA==\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-transfer-encoding;\r
+ bh=PYSMaeeFe8i1SzU/yZqXaYUErh4YI6HCHYLp41fuReo=;\r
+ b=PNw+h5nru19ohIGKHWwuB2FleV3NaUmnys/PV+Zi27T1Qq9lP5Wq/ean/3BaAgl2rh\r
+ vgCbDTtWy6kIbyX9Yd98UM8RvtZTOgl6FKqCY/MTphuTlStSYEJ4ajzsNYquIrmvlwNY\r
+ HsvYFP/PKE6anOvMsWeN5d///oDuV8j2k6OVWt2Wx8m6PMA8f4hQPZl0g5dyOHmcJ2hH\r
+ +m0Og7nmFQz3q4JoQBaaoQbmmrm2JpmmyitypjJiBCGTIv3eJgp1KZEuRg2U5FnIDVss\r
+ Zce/sx8m4xF0UITUqWGMtpSZzZ2D6O60C+VG3ZDWt/T4O0EMErdyuSG5mr1QFagj3c+c\r
+ wLRg==\r
+X-Gm-Message-State:\r
+ AD7BkJKIYPSSBQnhKQtJfen4A4yqyaxNJ4nCqt5do4JvFdX78Pm4O9NyEoJFruzCw81JBg==\r
+X-Received: by 10.25.31.193 with SMTP id f184mr471754lff.5.1456487442757;\r
+ Fri, 26 Feb 2016 03:50:42 -0800 (PST)\r
+Received: from localhost (c6878BF51.dhcp.as2116.net. [81.191.120.104])\r
+ by smtp.gmail.com with ESMTPSA id f196sm1791024lfb.49.2016.02.26.03.50.41\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Fri, 26 Feb 2016 03:50:41 -0800 (PST)\r
+Date: Fri, 26 Feb 2016 11:50:41 +0000\r
+From: Gaute Hope <eg@gaute.vetsj.com>\r
+Subject: Re: how do the different frontends deal with displaying large\r
+ queries?\r
+To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org\r
+References: <1456296267-astroid-0-gqidxpyulu-23762@strange>\r
+ <87ziuqj8xl.fsf@tesseract.cs.unb.ca>\r
+In-Reply-To: <87ziuqj8xl.fsf@tesseract.cs.unb.ca>\r
+User-Agent: astroid/v0.5-59-g23e14430 (https://github.com/gauteh/astroid)\r
+Message-Id: <1456487129-astroid-1-zemv9qfkbh-18628@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: Fri, 26 Feb 2016 11:50:48 -0000\r
+\r
+David Bremner writes on February 24, 2016 18:48:\r
+> Gaute Hope <eg@gaute.vetsj.com> writes:\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
+>\r
+> I only know the emacs front end, and I suspect the answer won't help you\r
+> much. We start filling an emacs buffer asynchronously with the results,\r
+> and display the top of the buffer with the first results.  Results are\r
+> appended to the end of the buffer, typically much faster than the user\r
+> can scroll.\r
+\r
+Hi,\r
+\r
+I am testing out this way of loading threads, however, I run into an\r
+issue which I have been bugging you with before:\r
+\r
+While loading the threads, if I make enough modifications to the\r
+database while the query is still loading (specifically 1: removing the\r
+unread tag from a thread, and 2: adding the unread tag to the same thread)\r
+apparently the query is invalidated in some way, and I get a hard crash\r
+in `notmuch_tags_get ()`.\r
+\r
+The thread in question has alreaday been loaded and is displayed.\r
+\r
+Do you deal with this issue in some way?\r
+\r
+[ code in question: https://github.com/gauteh/astroid/pull/95 ]\r
+\r
+Regards, Gaute\r
+\r
+=\r