From: Roderick Schertler <roderick@gate.net>
Subject: full threads from gnus-fetch-old-headers?
Date: Tue, 21 May 1996 16:33:23 -0400 [thread overview]
Message-ID: <13573.832710803@eeyore.ibcinc.com> (raw)
I've got gnus-fetch-old-headers and gnus-build-sparse-threads both set
to t, but I'd like to see even more of the thread data while I'm reading
news. I'm using Sgnus 0.89 with nnspool.
My news server often receives responses before the posts they're
following up to. Is there some way that I can get entire threads to
show up in the summary or tree buffers, rather than just those articles
needed to hold threads together? That is, I'd like to see not only the
articles which precede the unread ones, but articles which are responses
to them as well. (Ideally, I'd like to be able to have the entries for
every single article in a thread present in the tree buffer (plus the
summary buffer if need be) whenever I've selected even a single article
in the thread.)
More concretely, my problem is this: I like to answer questions in
comp.lang.perl.misc. If I read the response to a question a couple of
days before the question comes in, then when I read the question itself
there's no indication in the summary buffer that the question has
already been answered. If I don't happen to remember reading the
response a few days ago then I'm liable to give a duplicate answer. I'm
looking for a way to see that the article I'm reading has some replies,
even though I read the replies a few days ago.
Can this be done with Gnus as it stands? If not could this be put on
the Red wish list?
Thanks for any help.
--
Roderick Schertler
roderick@gate.net
next reply other threads:[~1996-05-21 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-21 20:33 Roderick Schertler [this message]
1996-05-22 0:25 ` Lars Magne Ingebrigtsen
1996-05-22 14:11 ` Per Abrahamsen
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=13573.832710803@eeyore.ibcinc.com \
--to=roderick@gate.net \
/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).