Date: Fri, 26 Feb 2016 11:50:41 +0000
From: Gaute Hope <eg@gaute.vetsj.com>
Subject: Re: how do the different frontends deal with displaying large
 queries?
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
References: <1456296267-astroid-0-gqidxpyulu-23762@strange>
 <87ziuqj8xl.fsf@tesseract.cs.unb.ca>
In-Reply-To: <87ziuqj8xl.fsf@tesseract.cs.unb.ca>
User-Agent: astroid/v0.5-59-g23e14430 (https://github.com/gauteh/astroid)
Message-Id: <1456487129-astroid-1-zemv9qfkbh-18628@strange>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: list

David Bremner writes on February 24, 2016 18:48:
> Gaute Hope <eg@gaute.vetsj.com> 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.

Hi,

I am testing out this way of loading threads, however, I run into an
issue which I have been bugging you with before:

While loading the threads, if I make enough modifications to the
database while the query is still loading (specifically 1: removing the
unread tag from a thread, and 2: adding the unread tag to the same thread)
apparently the query is invalidated in some way, and I get a hard crash
in `notmuch_tags_get ()`.

The thread in question has alreaday been loaded and is displayed.

Do you deal with this issue in some way?

[ code in question: https://github.com/gauteh/astroid/pull/95 ]

Regards, Gaute

=