Re: asynch prefetch backtrace

[Simon Josefsson <jas@extundo.com>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Yes, that seem to be the case.  (That's odd.  I really thought that
>> the async stuff should work for all backends.  Do I misremember
>> totally?  Am I misreading the code?  I have a suspicion that there's
>> something I'm not remembering...)
>
> Ah, now I know.  Most gnus-async doesn't know anything about the
> method the back end is using to fetch the articles (which is proper),
> but the new function (well, from 1998) `gnus-async-wait-for-article'
> does look deep into backend internals.  Which is a bug.
>
> The point of that function is to see whether we're trying to select
> the article which is just arriving in the async buffer, and if so,
> wait until it's arrived.
>
> The easy fix for this is to just move the function to the back end,
> define a new back end interface function, and have gnus-async call
> that instead.

But asynchronous prefetching has worked for ages, with nnimap too, and
now it normally works but not when there is a very large article in
the summary buffer.  Weird.

Is anyone else seeing this?  Maybe I have broken something locally.