From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Cc: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>, ding@ifi.uio.no
Subject: Re: how do you subscribe to new groups if I don't save-killed
Date: 24 Mar 1996 00:34:56 +0000 [thread overview]
Message-ID: <w8shgvfz5u7.fsf@ylfing.ifi.uio.no> (raw)
In-Reply-To: gsstark@MIT.EDU's message of 18 Mar 1996 22:34:12 -0500
gsstark@MIT.EDU (Greg Stark) writes:
> Well I would like to subscribe to a bunch of newsgroups;
> say i've taken a sudden interest in comp.lang newsgroups.
> I want to hit 9Amcomp.lang and then just subscribe and kill
> groups as desired.
>
> Currently i can do that if I have some settings of -SAVE-KILLED
> and -READ-ACTIVE-FILE, but i don't know which combinations.
> And if it doesn't start with enough information, even commands
> like -FIND-NEW-NEWSGROUPS won't make it start working.
>
> This seems inconsistent and undesirable. I admit doing LIST-ACTIVE seemed
> really slow, i guess active-file parsing is one place to look for speed
> optimizations.
No, parsing the active file is quite fast. Reading it is *slow*; it's
typically ~300kb long.
`A m' lists groups on various levels, and groups that aren't
subscribed, zombies, killed or unsubscribed aren't on any levels.
Perhaps we should add a level 10 for these groups? `1 0 A m' would
then work as one would suppose.
On the other hand, one could just add a regexp parameter to
`gnus-group-list-active' -- `A A'. `C-u A A comp.lang RET' would then
do the trick. I've added this to the Red Gnus todo list.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1996-03-24 0:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-20 14:58 Greg Stark
1996-02-20 23:05 ` Lars Magne Ingebrigtsen
1996-02-21 19:24 ` Patrick J. LoPresti
1996-02-21 20:42 ` Shane Holder
1996-02-21 21:11 ` Patrick J. LoPresti
1996-02-21 22:16 ` Shane Holder
1996-02-22 1:12 ` Lars Magne Ingebrigtsen
1996-02-21 19:49 ` Greg Stark
1996-02-22 6:01 ` Lars Magne Ingebrigtsen
1996-02-28 7:41 ` Greg Stark
1996-02-29 8:57 ` Lars Magne Ingebrigtsen
1996-02-29 15:59 ` Greg Stark
1996-03-01 9:04 ` Lars Magne Ingebrigtsen
1996-03-01 19:23 ` Greg Stark
1996-03-17 13:13 ` Lars Magne Ingebrigtsen
1996-03-17 15:10 ` Thomas Neumann
1996-03-19 3:34 ` Greg Stark
1996-03-24 0:34 ` Lars Magne Ingebrigtsen [this message]
1996-03-29 0:08 ` Greg Stark
1996-03-29 16:11 ` Lars Magne Ingebrigtsen
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=w8shgvfz5u7.fsf@ylfing.ifi.uio.no \
--to=larsi@ifi.uio.no \
--cc=ding@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).