Re: Strange auto-caching

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> 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.

I've now done that in a group which has some wrongly-displayed
articles.  There was also a new article that was unfetched (and
correctly marked as such).

Selecting the new article changed it to mixed case and updated the %O
mark from - to +, as it should.  So it seems that the fetching
updates the article line.

Selecting any other lines (those where %O was + and also those where
%O was - and thus wrong) did not change the case.  Only the color
changed according to readed-ness state and the %U mark changed.

Does that tell you anything?  It doesn't tell me anything.


PS: On a tangent, have I ever mentioned that ticked (and thus,
    cached -- cf. gnus-use-cache) articles are always displayed as
    not fetched, except during the Gnus session when I hit `u'?
    Directly after I hit `u' on them, they are in red as they should
    be, but in later Gnus sessions, the %O mark changes and the red
    color goes away (to be replaced by the undownloaded face).
-- 
A turnip curses Elvis