Re: Including cached messages automatically?

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

Simon Josefsson <jas@pdc.kth.se> writes:

> Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> 
> > Hence, I do (add-hook 'gnus-summary-generate-hook
> > 'gnus-summary-limit-include-cached), but this has strange effects.
> 
> `g-s-limit-include-cached' require a summary buffer to work, and the
> summary buffer hasn't been generated yet when that hook is called.
> 
> (add-hook 'gnus-summary-prepared-hook 'gnus-summary-limit-include-cached)

Hm.  I can't reproduce the strange `doubled message' behavior.  I
think it might have to do with messages which are both ticked and
cached -- maybe that's why they are included twice.  I'll check soon.

But the above line has a different problem: when entering a group with
SPC (auto-select-first is on), and if there are cached messages before
the first unread one, then point will be on the wrong message.  As an
example, suppose that there are some cached messages, then two old
(ancient) ones, and then comes the first unread message.  Then the
first unread message will be shown but point will be on the third line
in the summary buffer.  (Apparently because it would have been on the
third line if it weren't for the cached messages.)

Entering a group with RET, then using `.' to select the first message,
works fine.

PS: Why do I have messages which are both ticked and cached?  Well,
that's because I switched from gnus-use-cache equal t to
gnus-use-cache equal passive a short time ago.

kai
-- 
This gubblick contains many nonsklarkish English flutzpahs,
but the overall pluggandisp can be glorked from context. -- David Moser