Re: Strange auto-caching

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> What I found occurred when several articles were marked as
>> downloadable.  In this case, the current line points to the the last
>> marked article.
>
> Does this happen when I do `@' or `J #' in the summary buffer?  I
> never do that.

OK, I went back to your original post.  It appears that you always
fetch articles by selecting them.  That means that you're always
calling gnus-agent-fetch-selected-article.

The main part of that function performs three actions:
1) It calls gnus-agent-fetch-articles (Fetching has nothing to do with
   the summary data structures so this shouldn't have anything to do
   with your problem).
2) It uses delq to remove the current article from the
   gnus-newsgroup-undownloaded list (This is so simple that I can
   guarantee that it is not the problem :) ).
3) It calls gnus-summary-update-article-line.

I know that you don't want to consider that g-s-u-a-l is the problem.
However, I believe that you can test it fairly easily.

I'd like you to do the following in your summary buffer.

M-: (let ((inhibit-read-only t)) (upcase-region (point-min) (point-max)))

This will upcase your entire summary.  It will look ugly but it will
sure help ID any changes to the text.  Now, try to read some of the
unfetched articles.  If g-s-u-a-l is working correctly the selected
article's line will refresh to mixed-case.  If it isn't working
correctly, some other line will refresh.

Let me know what happens when the download status is wrong.

Kevin