From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: gnus-fetch-old-headers = some, but no old headers fetched?
Date: Fri, 17 Aug 2001 22:36:39 +0200 [thread overview]
Message-ID: <vafhev64e5k.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vaf3d6qv7fk.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 17 Aug 2001 20:59:43 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 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...
Indeed, gnus-build-sparse-threads sounds just like the description
above. Now I only need to figure out the right balance between too
few lines and too many lines.
Very nice. For some reason, I thought that gnus-build-sparse-threads
wasn't what I wanted. But now it seems to be *just* what the doctor
ordered.
I'm happy.
kai
--
~/.signature: No such file or directory
prev parent reply other threads:[~2001-08-17 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 8:59 Kai Großjohann
2001-08-13 14:50 ` Janne Rinta-Manty
2001-08-13 15:55 ` Kai Großjohann
2001-08-14 13:29 ` Amos Gouaux
2001-08-17 17:09 ` Lars Magne Ingebrigtsen
2001-08-17 18:59 ` Kai Großjohann
2001-08-17 19:33 ` Lars Magne Ingebrigtsen
2001-08-17 20:36 ` Kai Großjohann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafhev64e5k.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).