From: Steinar Bang <sb@metis.no>
Subject: 5.8.3 (CVS version) NNTP primary server stops updating unread number
Date: 16 Mar 2000 09:27:07 +0100 [thread overview]
Message-ID: <whaejz5nhg.fsf@viffer.metis.no> (raw)
My problem, is that a normal
g
in the *Group* buffer no longer updates the unread number on the NNTP
groups on the primary server (I only have this one NNTP server).
After the get command I see the text "nntp read: 15k" for a while in
the minibuffer, until it moves on to the secondary servers (nnml and
an nnimap server).
I can update the NNTP groups individually with
M-g
but that is impractical in the long run.
Here's what I did:
Yesterday I decided to try nnslashdot. When I did my first
A z
it listed a hug amount of zombie groups.
S z
killed them, but also killed the nnslashdot groups.
Due to a bit of clumsyness on my part, a big number of the zombie
groups were subscribed, so I had to unsubscribe them, after I took an
l
to show the normal list of groups.
Since I wanted to try out slashdot, without waiting for new groups to
appear, I stopped Gnus, and removed the nnslashdot groups from
gnus-killed-list, in ~/.newsrc.eld, and then restarted Gnus.
This seemed to work, except I occasionally get the hanging in 'Mark
set' that others have reported, so I have now removed it.
My guess is that somewhere in there, I messed up a setting in
~/.newsrc.eld. But I have no clue about where to look.
Any hints and ideas welcome!
- Steinar
next reply other threads:[~2000-03-16 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-16 8:27 Steinar Bang [this message]
2000-03-21 6:56 ` Steinar Bang
2000-03-21 7:45 ` Steinar Bang
2000-03-21 8:23 ` Steinar Bang
2000-03-21 9:47 ` Steinar Bang
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=whaejz5nhg.fsf@viffer.metis.no \
--to=sb@metis.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).