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

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

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>>> IIRC Gnus fetches old headers, but then gnus-cut-threads throws away
>>> "uninteresting" articles from the beginning of the threads.  At least
>>> I have a brutal (commented out) (eval-after-load "gnus-sum" '(fset
>>> 'gnus-cut-threads 'identity)) in my .gnus from the time I tried 'some.
>>
>> Ick.  Gnus shouldn't do that.  Argh.  Maybe I should include a
>> variable.
>
> 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.  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?

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.

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

kai
-- 
~/.signature: No such file or directory