Gnus development mailing list
 help / color / mirror / Atom feed
From: Ami Fischman <usenet@fischman.org>
Subject: gnus (cvs) decides to make nntp groups "mail" groups
Date: Sat, 05 Jan 2002 14:19:28 -0800	[thread overview]
Message-ID: <81heq08mq7.fsf@zion.bpnetworks.com> (raw)

For some reason, gnus seems to decide to consider random foreign nntp groups
as mail groups.  The symptom that got me to debug this was that as of 2 days
ago, nntp+news.gnus.org:gnus.ding kept coming up with >37000 unread
articles.  I know y'all are talkative, but it seemed a bit much even for
this group :).  So, I look in ~/.newsrc.eld, and I see that the third
element in the gnus.ding group (the one following the level) is (1 . 2). Ah
ha, say I to myself, the count got messed up somehow.  So fine, I change
that "2" to 38700 or so.  Restart gnus, and lo, nothing's changed!  Looking
at .newsrc.eld again, I see that it's back at (1 . 2).  Tried a few more
times (to make sure I was really saving, exiting, restarting in the right
order).  A couple of days pass, and now it's the weekend so I have time to
look into this further: somehow, this group made it into my ~/mail/active
file, with a line saying:
nntp+news.gnus.org:gnus.ding 1 1 y

Deleting the line makes gnus honor my changes to .newsrc.eld.  There were
two other non-nnml groups in my ~/mail/active file:

nntp+news.verio.net:gnu.emacs.help 37406 37406 y
nntp+news.opera.no:opera.linux 7871 7871 y

They are both groups I read, and I've had similar issues (where the group
shows up completely unread) with both, but killing and resubscribing solved
the problem before (I think).

So, why is gnus putting these nntp groups in ~/mail/active?  Once it does
so, why is it honoring the information there?

I am using oort 0.05 cvs as of this morning w/ gnu emacs 21.1.

-- 
  Ami Fischman
  usenet@fischman.org




             reply	other threads:[~2002-01-05 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-05 22:19 Ami Fischman [this message]
2002-01-19 19:57 ` Lars Magne Ingebrigtsen
2002-01-19 22:35   ` Ami Fischman

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=81heq08mq7.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).