From: Xavier Maillard <zedek@gnu-rox.org>
Subject: nnrss problem: old become new ??
Date: Sun, 30 May 2004 19:42:35 +0200 [thread overview]
Message-ID: <plop87zn7pstf8.fsf@gnu-rox.org> (raw)
Hello,
As a heavy nnrss user, I'd like to see some improvements.
Maybe it is already done and I don't use it the right way...
So let's begin.
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 ! This is quite
annoying because it forces me to enter the group to check what is new.
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 ?
For instance, whenever I read an article, I clearly see the 'R' mark, I
still can set the 'E' 'r' ... marks. Exiting the group and returning
into it is ok. But whenever I g-g-n (ie. 'g' in the group server), the
contents of my nnrss groups are updated with bad informations.
SOmething weird: if I tick a read message, exit the group and g-g-n,
the ticked article is not shown as new (and unread) but is still ticked.
It seems only ticked articles are ok but others aren't.
I don't know if it is doable or not but my guess is that it shouldn't
be too hard to implement this.
Once again, maybe I misuse it and in this case I would like you to help
me configure it.
Regards,
--
Registered Linux-User #340967 with the Linux Counter, http://counter.li.org.
next reply other threads:[~2004-05-30 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 17:42 Xavier Maillard [this message]
2004-05-30 18:24 ` Jesper Harder
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=plop87zn7pstf8.fsf@gnu-rox.org \
--to=zedek@gnu-rox.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).