Re: mismatching summary buffer lines and article content?

[ludo@gnu.org (Ludovic Courtès)]

Hi,

Simon Josefsson <simon@josefsson.org> writes:

> Simon Josefsson <simon@josefsson.org> writes:
>
>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>
>>> Simon Josefsson <simon@josefsson.org> writes:
>>>
>>>> Yes, I'm using the same hook.  Sometimes I have the feeling that it is
>>>> also related to async pre-fetching, but I'm not sure -- sometimes the
>>>> article content has been garbage looking like NOV lines.  That's when I
>>>> restart Gnus and it is gone.
>>>
>>> Yeah, I've seen the "article not matching up with the summary buffer"
>>> thing in NNTP groups, too.  But I've been totally unable to reproduce
>>> it, and I haven't seen any obvious bugs in the code, either, so it's
>>> really difficult to fix.
>>>
>>> My main suspect is the async pre-fetch code, too, but there may also be
>>> interactions between the Agent and the pre-fetch code.  Oy vey.
>>>
>>> Oh, I see that `gnus-asynchronous' defaults to nil?  Hm, I think it
>>> should default to t...  Anyway, could you try setting that to nil and
>>> see whether the problems disappear?  
>>
>> I can try -- however I have tried another thing for a while now that
>> seems to have made the problem go away: removing
>> gnus-agent-fetch-selected-article from gnus-select-article-hook.  I
>> removed the hook on 28 February and I don't recall seeing the problem
>> since then.
>>
>> I'll add the hook back now and see if I start to notice the problem
>> again.  When I have seen the problem a few times, I'll disable
>> gnus-asynchronous to see if that also independently fixes the problem.
>
> Re-enabling gnus-agent-fetch-selected-article made the problem come
> back: I have seen the problem several times since the email above on
> March 7th.
>
> I have now disabled gnus-asynchronous.

I have ‘gnus-asynchronous’ to nil and I see the problem from time to
time (on an nnimap group with the agent enabled.)

Thanks,
Ludo’.