From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: something I've always wanted...
Date: Fri, 05 Apr 2002 10:32:28 -0500 [thread overview]
Message-ID: <vxk8z82b1pv.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <871yduqisw.fsf@alum.wpi.edu> (Josh Huber's message of "Fri, 05 Apr 2002 10:14:23 -0500")
Given what information is acquired when, yes, it's very hard. If you
want a *Group* buffer indication, the problem is that Gnus has no idea
of group content when creating the *Group* buffer. All Gnus knows is
the minimalist data point, "there are articles here numbered between X
and Y."
For Gnus to know more than that, you would require Gnus to enter each
group and effectively do *Summary* generation on every single group,
without displaying the summaries, but using the information learned to
modify the *Group* display.
What you want is possible, but it's bound to be alarmingly expensive
and slow, especially when (as you said) you are subscribed to oodles
of forums.
next prev parent reply other threads:[~2002-04-05 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 15:14 Josh Huber
2002-04-05 15:32 ` Karl Kleinpaste [this message]
2002-04-05 16:41 ` Matthieu Moy
2002-04-05 18:05 ` Derrell.Lipman
2002-04-05 18:27 ` Karl Kleinpaste
2002-04-05 20:36 ` Josh Huber
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=vxk8z82b1pv.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).