From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Can the tree show the _whole_ thread?
Date: 01 Feb 1996 19:48:58 +0100 [thread overview]
Message-ID: <w8ska26j2zp.fsf@aegir.ifi.uio.no> (raw)
In-Reply-To: Jason L Tibbitts III's message of 31 Jan 1996 21:42:36 -0600
Jason L Tibbitts III <tibbs@uh.edu> writes:
> I.e. I can see the whole conversation, but some of the articles are old
> (like "(Bla)" and "(Urk)") or have expired (like the root) and the summary
> buffer is really simple. Is this possible? Somehow I think it's not,
> given that both buffers work from the same information and the summary
> buffer always displays everything in the list of threads. Perhaps for Red
> Gnus?
You're right that it isn't currently possible, but all that needs to
be done is having the tree generation functions ignore
`gnus-newsgroup-limit', which is the variable that says what articles
should be visible. I've added this to the Red Gnus todo list.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-02-01 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-01 3:42 Jason L Tibbitts III
1996-02-01 18:48 ` Lars Magne Ingebrigtsen [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=w8ska26j2zp.fsf@aegir.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).