Gnus development mailing list
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: ding@gnus.org
Subject: Re: what's up with me reading comp.infosystems.www.authoring.cgi?
Date: 18 Apr 2001 15:08:50 -0700	[thread overview]
Message-ID: <m1bsptj1xp.fsf@halfdome.holdit.com> (raw)
In-Reply-To: <vxku23mrt76.fsf@cinnamon.vanillaknot.com>

>>>>> "Karl" == Karl Kleinpaste <karl@charcoal.com> writes:

Karl> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>> group comp.infosystems.www.authoring.cgi
>> 211 1123 85842 86964 comp.infosystems.www.authoring.cgi group selected
>> Fine... looks like highest article is 86964.  Now I look at group parameters
>> for that group after a "C y":
>> ("comp.infosystems.www.authoring.cgi" 3
>> ((1 . 91940)))

Karl> See if "list active comp.whatever" gives consistent results.

Karl> There are circumstances in which these numbering reports vary,
Karl> stupidly and inconsistently.

Karl> Gnus uses "group" on group entry but "list" elsewhen.

    200 Supernews NNRP server ready - http://www.supernews.com (posting ok)
    group comp.infosystems.www.authoring.cgi
    211 1127 85842 86968 comp.infosystems.www.authoring.cgi group selected
    list active comp.infosystems.www.authoring.cgi
    215 list follows
    comp.infosystems.www.authoring.cgi 0000086968 0000085842 m

Nope.  Same range.  Next idea?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!


  reply	other threads:[~2001-04-18 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 15:47 Randal L. Schwartz
2001-04-18 17:52 ` Karl Kleinpaste
2001-04-18 22:08   ` Randal L. Schwartz [this message]
2001-04-18 22:12     ` Karl Kleinpaste
2001-04-18 23:40       ` Randal L. Schwartz
2001-04-19 10:34         ` Florian Weimer

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=m1bsptj1xp.fsf@halfdome.holdit.com \
    --to=merlyn@stonehenge.com \
    --cc=ding@gnus.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).