From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Changed criteria for deciding if articles have been read?
Date: 01 Oct 2001 18:30:56 -0400 [thread overview]
Message-ID: <m24rpj802n.fsf@asfast.com> (raw)
In-Reply-To: <m24rpjqavv.fsf@asfast.com>
Lloyd Zusman <ljz@asfast.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> [ ... ]
>
> After running the new version, no `.mrk/.marks' had been created
> anywhere, but I didn't do the `nnml-generate-nov-databases'. Would
> I have to do that before any .mrk/.marks appear?
Aha! I discovered that there *are* indeed a bunch of `.marks' files,
each of which appear in their respective group directory (however, not
under any directory named `.mrk'). For example, for my `gnus' nnml
group, the following file exists:
~/Mail/gnus/.marks
It was last created/modified on Aug. 19, which is the last time I
attempted to run a new version of Oort (but I didn't continue using
it, due to an unrelated problem, and I went back to the older version
which is still the version I'm using now). No doubt this Aug. 19
version of Oort created these `.marks' files when it started up.
The `.marks' file I mentioned above contains this data (it's all on a
single line in the file, but I'm wrapping it here):
((read (1 . 26024))
(reply 24924 25041 25273 25295 25306 (25310 . 25311) 25329 25337)
(tick 26017 26020))
Funny how it just _happens_ to contain the same info that `G E' shows
below for the "recent Oort version" case. :)
I then renamed all my `.marks' files in all of my group directories,
and I once again started up the recent version of Oort. Without those
old `.marks' files, the unread-ness of my articles is now once again
correct. And then, after exiting the recent version of Oort, there
was now a zero-length `.marks' file in that same group directory.
So ... for those people who are transitioning from an older to a more
recent version of Oort, and who see this same inconsistency concerning
unread articles, I recommend that you search in your group directories
for any `.marks' files that are laying around, and delete them.
Does this solve the problem, or does it just illustrate another aspect
of a bug?
> Results of `G E' in older Oort version
> (group buffer shows no unread messages for this group):
>
> ;;; Editing the group info for `nnml+email:gnus'.
> ;; Type `C-c C-c' after you've finished editing.
>
> ("nnml+email:gnus" 2
> ((1 . 27024))
> ((reply 26994 27004)
> (tick 27000 27023))
> "nnml:email"
> ((to-address . "ding@gnus.org")
> (to-list . "ding@gnus.org")
> (total-expire . t)
> (expiry-wait . 30.0)))
>
> Results of `G E' in very recent Oort version:
> (group buffer shows 591 unread messages for this group):
>
> ;;; Editing the group info for `nnml+email:gnus'.
> ;; Type `C-c C-c' after you've finished editing.
>
> ("nnml+email:gnus" 2
> ((1 . 26433))
> ((reply 24924 25041 25273 25295 25306
> (25310 . 25311)
> 25329 25337)
> (tick 26017 26020))
> "nnml:email"
> ((to-address . "ding@gnus.org")
> (to-list . "ding@gnus.org")
> (total-expire . t)
> (expiry-wait . 30.0)))
>
>
> --
> Lloyd Zusman
> ljz@asfast.com
>
>
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~2001-10-01 22:30 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
2001-10-01 22:00 ` Lloyd Zusman
2001-10-01 22:30 ` Lloyd Zusman [this message]
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=m24rpj802n.fsf@asfast.com \
--to=ljz@asfast.com \
/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).