From: Michael Powe <michael+gnus@trollope.org>
Subject: Re: Searching for groups?
Date: Sat, 31 May 2003 10:30:12 -0400 [thread overview]
Message-ID: <87add3qjd7.fsf@cecilia.trollope.org> (raw)
In-Reply-To: <m3znl7ka5q.fsf@sbcglobal.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Harry" == Harry Putnam <reader@newsguy.com> writes:
Harry> Michael Powe <michael+gnus@trollope.org> writes:
>>>>>>> "Harry" == Harry Putnam <reader@newsguy.com> writes:
>>
Harry> Michael Powe <michael+gnus@trollope.org> writes:
>> >> actually, this is not well-implemented on gnus. you
>> basically >> have to load the active file and search it. i've
>> tried 'A M' >> but i either have the wrong idea (that it will
Harry> A M works for me in version 5.10.3 (cvs). It finds all
Harry> matching groups in Active file or at least in Killed and
Harry> Zombie lists. Including mail groups.
>> oh well, if i go into the *Group* buffer and type 'A M'
>> (capital-A capital-M) and search 'comp.os.' or 'comp.os.*' or
>> even 'comp\.os\..*', all i get are the handful of
>> 'comp.os.linux' newsgroups to which i am subscribed.
>> however, if i search 'alt\.' i get a huge list of alt.* groups;
>> if i search 'comp\.' i get
>> 0: comp.security.pgp.test Z 51: it.comp.lang (m) Z 120:
>> it.comp.lang.assembly Z 400: it.comp.lang.python Z 612:
>> it.comp.sicurezza.crittografia Z 1325: it.comp.software.p2p Z
>> 204: it.comp.www.server Z 493: tw.bbs.comp.lang.php
>> all of which seems whacky to me, as i don't read italian or
>> chinese. ;-)
Harry> I doubt the nntp server sysadmin cares what languages you
Harry> are fluent in when the active list is compiles.... hehe.
;-)
Harry> You didn't say what version of gnus. Or maybe I missed it.
Harry> Does `A A' get a complete list? Maybe for interim until
Harry> you find the problem you could `A A' and then M-x occur
Harry> REGEX
Gnus v5.10.2
Harry> Or at least press `g' on in the server buffer and save the
Harry> list then grep it as and when necessary.
Harry> Your settings regarding what gnus does with groups you
Harry> aren't subscribed to may be related. I noticed A M finds
Harry> Zombies and Killed groups.
no idea what i might have set that would affect this. i don't have
much in the way of customization, actually, except in posting-styles.
in fact, i see even that is mostly commented out now.
'A A' does get the complete list, that is usually what i have to do
when i want to look for a group, 'A A' and then C-s. it works, it's
just not efficient.
mp
- --
Michael Powe michael@trollope.org Waterbury CT USA
"Usenet is like a herd of performing elephants with diarrhea --
massive, difficult to redirect, awe-inspiring, entertaining, and a
source of mind-boggling amounts of excrement when you least expect
it." -- Gene Spafford
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+2Lx2UFRfMHc4lysRAlRdAJ9eItF3S1+wE0ZvyRwbrmozOm/I9gCgqKi6
sfh8lb+3vw2GIxAujwiu1kc=
=7SM4
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-05-31 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m365ogbz8j.fsf@localhost.localdomain>
[not found] ` <87znlcjg8d.fsf@cecilia.trollope.org>
[not found] ` <m3smr3xyg7.fsf@sbcglobal.net>
[not found] ` <87add98xed.fsf@cecilia.trollope.org>
2003-05-28 3:44 ` Harry Putnam
2003-05-31 14:30 ` Michael Powe [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=87add3qjd7.fsf@cecilia.trollope.org \
--to=michael+gnus@trollope.org \
/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).