From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: agent corrupting .overview/.agentview
Date: 08 Sep 2000 19:02:31 +0200 [thread overview]
Message-ID: <ilupumeyfyw.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <qwwwvgt1ghf.fsf@sap.com>
Christoph Rohland <cr@sap.com> writes:
> Hi,
>
> Apparently the agent does not handle the case right when does get the
> same article several times:
>
> The first time I experienced this when I applied Simon's patch to
> include readedness into the category predicates: As soon as I included
> some read articles into the category it came up with corrupted
> overview files.
>
> Today I had the same with a standard setup. I investigated some more
> and found, that one article was 16 times included in
> News/agent/nnimap/unnamed/INBOX/.overview.
Yes, I've been seeing this too. However, it should not cause any
problems in itself (other than wasting space). I'm working on this
tonight.
> It also was 16 time in .agentview, but .agentview was not sorted,
> .overview was. This apparently leads to an 'unexpected end of buffer
> *Gnus agent overview*'.
Ouch, this might explain the problem with re-fetching articles in the
first place. Thanks for spotting that.
prev parent reply other threads:[~2000-09-08 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-03 18:24 Christoph Rohland
2000-09-08 17:02 ` Simon Josefsson [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=ilupumeyfyw.fsf@barbar.josefsson.org \
--to=simon@josefsson.org \
--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).