From: Karl Eichwalder <keichwa@gmx.net>
Cc: ding@gnus.org
Subject: Re: nntp articles wrongly marked as read ('O')
Date: Wed, 02 Jul 2003 20:38:03 +0200 [thread overview]
Message-ID: <shof0cbwqc.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <86el2t3heb.fsf@i3d.home> (Robert Epprecht's message of "Tue, 20 May 2003 14:57:16 +0200")
Robert Epprecht <epprecht@solnet.ch> writes:
> I don't know if this could be the same bug, but I still see occasionally
> some messages marked as read (*and* unseen!) in *nnml* groups. Last time
> it happened maybe three weeks ago with CVS head of this date. The messages
> have just been split by nnmail-split-methods and when I enter the group
> some messages shows up as read. The agent is *not* involved, as this happens
> in a mail-only incarnation of Gnus with (setq gnus-agent-cache nil) and
> (setq gnus-agent nil) in .gnus.el.
I can confirm this behavior. It often seems to happen if you receive
an answer to within a thread where the old messages were already
intentionally marked as read _and_ when there is an unrelated but more
recent message ticked.
> It is an old and *very* annoying bug. I still have no clue what triggers
> it.
Yes, that's the problem. Whenever I try to trigger the bug manually,
it does not happen; but then, after some weeks, I enter my default nnml
group with 'C-u RET' and article I've never read are marked as read.
--
| ,__o
http://www.gnu.franken.de/ke/ | _-\_<,
ke@suse.de (work) / keichwa@gmx.net (home) | (*)/'(*)
next prev parent reply other threads:[~2003-07-02 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 7:49 Karl Eichwalder
2003-05-19 15:24 ` Kai Großjohann
2003-05-20 12:57 ` Robert Epprecht
2003-07-02 18:38 ` Karl Eichwalder [this message]
2003-07-05 19:16 ` Robert Epprecht
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=shof0cbwqc.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
--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).