Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: gnus forgets new mail
Date: Tue, 23 Apr 2002 11:21:45 +0200	[thread overview]
Message-ID: <vaf3cxmwz12.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87sn5nsf74.fsf@nwalsh.com> (Norman Walsh's message of "Mon, 22 Apr 2002 15:31:27 -0400")

Norman Walsh <ndw@nwalsh.com> writes:

> / Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) was heard to say:
>
> | Yes.  Please have a look at the newsgroup data (type `G E' (not `G
> | e')).  Also have a look at the active file, and at the overview file
> | (if there is one).
>
> Well, `G E' reports:
>
> ;;; Editing the group info for `nnml:misc'.
> ;; Type `C-c C-c' after you've finished editing.
>
> ("nnml:misc" 2
>  ((1 . 4669)) [...]
>
> which may be more meaningful to you than to me. The active file says:

I think it means that 1 through 4669 are marked as read.

> mercury:~/Mail$ grep misc active
> misc 4669 1 y

I think this says that the lowest article number is 1 and the highest
is 4669.

> The .overview file is more than 1Mb so I won't attach it hear. The
> first message in the .overview is 1; the last is 4669.

Good.

> | I'm guessing that Gnus thinks articles up to N are read, but the new
> | articles get numbers less than N.
>
> Yeah, that's what I thought too. But the active file seems to be
> up-to-date.

Hm.  So when a new message is added to the group, it gets number
4670, and is marked as read?

Strange, strange.

kai
-- 
Silence is foo!



  reply	other threads:[~2002-04-23  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 12:54 Norman Walsh
2002-04-22 14:31 ` Kai Großjohann
2002-04-22 15:31   ` Norman Walsh
2002-04-22 19:01     ` Kai Großjohann
2002-04-22 19:31       ` Norman Walsh
2002-04-23  9:21         ` Kai Großjohann [this message]
2002-04-23 14:23           ` Norman Walsh
2002-04-22 21:32 ` Robert Epprecht
2002-04-28 20:09 ` Norman Walsh

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=vaf3cxmwz12.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).