From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: nnrss problem: old become new ??
Date: Sun, 30 May 2004 20:24:48 +0200 [thread overview]
Message-ID: <m3n03p6adr.fsf@defun.localdomain> (raw)
In-Reply-To: <plop87zn7pstf8.fsf@gnu-rox.org> (Xavier Maillard's message of "Sun, 30 May 2004 19:42:35 +0200")
Xavier Maillard <zedek@gnu-rox.org> writes:
> I am always facing the same annoyance when reading RSS feeds withing
> Gnus. It seems Gnus is not able to keep track of my readings and always
> show me the old (read) entries as new (unread) ones !
>
> Is there any way I can prevent nnrss backend to act that way ? I mean
> can't it try to smartly track articles just the same as other
> backends ?
It works for me.
I don't know what's wrong in your setup, but as start you could look
in .newsrc.eld to see if the "seen" entries for rss are right.
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-05-30 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 17:42 Xavier Maillard
2004-05-30 18:24 ` Jesper Harder [this message]
2004-05-31 6:19 ` Xavier Maillard
2004-05-31 17:15 ` Jesper Harder
2004-06-01 5:02 ` Xavier Maillard
2004-06-01 11:34 ` Jesper Harder
2004-06-01 21:21 ` Xavier Maillard
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=m3n03p6adr.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).