Re: gnus-fetch-old-headers = some, but no old headers fetched?

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

>> That's, like, the difference between `all' and `some', isn't it?  Or
>> does `all' do more than "`some'-without-cutting-threads"?
>
> `all'?  I didn't even know that existed.

Er.  It doesn't.  I was thinking about the `display' thing, I think.
If you can call it thinking.

> I've got (setq gnus-fetch-old-headers t).  That fetches all the
> headers.  Does `some' also fetch all old headers, or just the ones
> referenced in the References headers of the new ones?

Everything is fetched in either case, but `some' prunes out anything
that's not related to what you would otherwise have seen.

That is, it only displays those articles that's needed to tie threads
together. 

> Actually, what I was after is this: fetch headers for unread messages,
> then fetch headers for the articles mentioned in the References
> headers, too.
>
> But maybe it was just wishful thinking on my part.

That would take *way* too long to be efficient, but one could have a
`more' setting that wouldn't be so aggressive when pruning.

> Hm.  Maybe gnus-build-sparse-threads does the trick?  I'll see...

It does other tricks.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen