Gnus development mailing list
 help / color / mirror / Atom feed
From: Ami Fischman <usenet@fischman.org>
Subject: bug in level code in latest oort
Date: Mon, 11 Mar 2002 17:30:15 -0800	[thread overview]
Message-ID: <81eliqindk.fsf@zion.bpnetworks.com> (raw)

Using CVS oort from couple of days ago w/ emacs 21.1.  I use level 2 for
nnml groups, level 3 for "close" nntp groups, and level 4 for "far" nntp
groups.  Thus, to check just my mail spool, I do "2 g" in the group buffer.
This works most of the time.  However, sometimes a "2 g" results in what
looks like would happen if I hit "20 g" -- all of the configured nntp
servers get queried, and zombie/killed groups are suddenly listed as well.
I can do a subsequent "2 l" to restrict the listing, but it is a major PITA
to have to wait for many faraway nntp servers to respond (the reason why I'm
using levels in the first place).  If I C-g in the middle of the querying of
the nntp's (actually, I need to hit C-g many times before it stops), some of
the nntp connections will get marked "(denied)" in the Servers buffer and
have to be manually re-O'd to be useful after that (in the current gnus
session).

Anyone seeing any similar symptoms?  Any idea what's up with this?

The only levels-related stuff in my .gnus is:

(custom-set-variables
 '(gnus-activate-level 2)
 '(gnus-level-default-subscribed 3))

and most of the time levels DO work correctly, so I don't think it's a
config error...

Thanks,
-- 
  Ami Fischman
  usenet@fischman.org




                 reply	other threads:[~2002-03-12  1:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=81eliqindk.fsf@zion.bpnetworks.com \
    --to=usenet@fischman.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).