Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Changed criteria for deciding if articles have been read?
Date: Mon, 01 Oct 2001 22:53:10 +0200	[thread overview]
Message-ID: <ilulmiv5bgp.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m2r8sorydl.fsf@asfast.com> (Lloyd Zusman's message of "30 Sep 2001 20:35:02 -0400")

Lloyd Zusman <ljz@asfast.com> writes:

> I just now did the CVS update, and when I run the resultant gnus
> build, I see many old articles in almost all my groups showing up as
> unread.
>
> The weird thing about this is that not all old articles show up as
> unread ... only maybe the past 3-5 weeks' worth.
>
> If I switch to my older version of Oort, the unread-ness of the
> articles once again appears correct.
>
> Are recent Oort versions doing something different with marks, or
> something?

Yes, Oort also keep marks in a .mrk/.marks file in nnfolder/nnml
groups.  Some said M-x nnml-generate-nov-databases RET fixed the
problem in the transition.  But maybe you could try debugging this, if
you can reproduce it by switching between versions, so that others
don't have to do M-x nnml.. RET.

For starters, in one group that triggers this, could you cut'n'paste
the content of `G E' (both new and old version) and the contents of
the .mrk/.marks file (new version)?




  parent reply	other threads:[~2001-10-01 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01  0:35 Lloyd Zusman
2001-10-01  6:09 ` Christoph Conrad
2001-10-01 20:53 ` Simon Josefsson [this message]
2001-10-01 22:00   ` Lloyd Zusman
2001-10-01 22:30     ` Lloyd Zusman
2001-10-02 11:43       ` Kai Großjohann
2001-10-02 11:53         ` Lloyd Zusman
2001-10-02 16:05           ` Kai Großjohann
2001-10-02 17:19             ` Simon Josefsson
2001-10-02 18:18               ` Dan Christensen

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=ilulmiv5bgp.fsf@barbar.josefsson.org \
    --to=jas@extundo.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).