Path: utzoo!utstat!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!samsung!uunet!mcsun!ukc!warwick!cudep From: cudep@warwick.ac.uk (Ian Dickinson) Newsgroups: news.software.b Subject: Re: Checkgroups problem Message-ID: <1990Aug8.113753.3487@warwick.ac.uk> Date: 8 Aug 90 11:37:53 GMT References: <1990Aug7.053447.19212@grian.cps.altadena.ca.us> Sender: news@warwick.ac.uk (Network news) Organization: Team Limpid's Death Mollusc From Hell - The Good Old Boys Lines: 34 In article tale@turing.cs.rpi.edu (David C Lawrence) writes: >I have a few problems with the way C News does it, and I've been >meaning to write this for Geoff just to have some things to think >about (perhaps one or two here he didn't realise or didn't have any >admin input on). The following comments all relate to C News checkgroups. I've been thinking about this recently too.... I agree with all of what David says and I have a few teenies to add. I wish I could place a hierarchy in the localgroups file, so I could say 'uw' or 'uw.all' instead of having to list each individual group. The alternative is to make sure a checkgroups message could be limited to the hierarchys mentioned as arguments, or the the hierarchy mentioned within the message. The latter is a botch though, seeing as there would be no way to totally remove a hierarchy. >checkgroups doesn't check moderated flags. I wish it did. In fact, >checkgroups doesn't care at all about flags. I modified mine to >consider 'x'ed groups as not really there. Ditto on = groups. Sounds nice. Unfortunately, rn pl47 does care about flags being more than a single character, and as soon as you set a group to be =othergroup rn thinks that it is bogus - not good :-( Looks like I'd better fix it. Cheers, -- \/ato. Ian Dickinson. GNU's not got BSE. When I grow up I want to be a vato@cu.warwick.ac.uk Plinth. Water Elemental. Shower me! vato@tardis.cs.ed.ac.uk Sabeq. gdd046@cck.cov.ac.uk "Nuke me tender, nuke me good!"