From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Agent: visual feedback about downloaded articles
Date: Mon, 21 Oct 2002 15:49:15 +0200 [thread overview]
Message-ID: <84wuob6gx0.fsf@crybaby.cs.uni-dortmund.de> (raw)
In-Reply-To: <uznt8npab.fsf@adobe.com>
Danny Siu <dsiu@adobe.com> writes:
> I found out that my some of my .overview files in the agent dir have
> duplicated entries (multiple lines with exact content) as a result
> of (setq gnus-agent-consider-all-articles t) always fetches read
> articles.
Do you think the duplicate lines come from
gnus-agent-consider-all-articles?
I'm hoping that this was because of old implementations and that the
current implementation does not add additional dupes.
How to deal with the existing dupes, though?
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-21 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 12:42 Kai Großjohann
2002-10-18 7:55 ` Danny Siu
2002-10-18 11:53 ` Kai Großjohann
2002-10-21 6:42 ` Danny Siu
2002-10-21 8:26 ` Kai Großjohann
2002-10-21 8:56 ` Danny Siu
2002-10-21 13:49 ` Kai Großjohann [this message]
2002-10-22 6:59 ` Danny Siu
2002-10-22 8:34 ` Kai Großjohann
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=84wuob6gx0.fsf@crybaby.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).