Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: nnrss problem: old become new ??
Date: Tue, 01 Jun 2004 23:21:28 +0200	[thread overview]
Message-ID: <plop87oeo33rfr.fsf@gnu-rox.org> (raw)
In-Reply-To: <m3wu2ry0is.fsf@defun.localdomain>

On  1 Jun 2004, Jesper Harder wrote:

> Xavier Maillard <zedek@gnu-rox.org> writes:
> 
> > On 31 May 2004, Jesper Harder wrote:
> > 
> > > Does this  mean that you have  multiple articles for  the same RSS
> > > item?
> > 
> > Not at the same time but  definetely yes, when g-g-n is done, my old
> > read content is back in the nnrss groups.
> 
> Do you do agressive expiration in the RSS groups? (if the old items

What do you mean ?? 

AFAIK, my current configuration is set like this:

1. (expiry-wait . immediate)
2. (expiry-target . delete)

My  nnrss groups  are not  auto-expirable  (explicitly set  to nil)  but
total-expire is on.

When I read an article, its mark  is set to 'R'. I can explicitly expire
articles by hand (ie 'E' on articles). When I leave a group, it is ok.

> are expired before the next g-g-n, then Gnus doesn't know that the
> items aren't new).

How can I verify what is the current marks state for a group ?

> Also, look at one of the *.el files ~/News/rss/ -- maybe you can
> figure out what's going on by examining it at different points.

Hmm, I will try to investigate a little further...
-- 
 In Gruuik we trust





      reply	other threads:[~2004-06-01 21:21 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
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 [this message]

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=plop87oeo33rfr.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).