From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: large .overview files in agentized nntp groups
Date: Sun, 20 Jan 2002 12:11:29 +0100 [thread overview]
Message-ID: <ilur8oluvj2.fsf@extundo.com> (raw)
In-Reply-To: <hv1ygl8s7j.fsf@rasputin.ws.nextra.no> =?iso-8859-1?q?(Bj=F8rn?= Mork's message of "Sun, 20 Jan 2002 07:14:08 +0100")
Bjørn Mork <bmork@dod.no> writes:
> Looks like this piece of code in gnus-agent-fetch-headers adds
> all articles with the 'seen' mark to the fetch list:
>
> ;; Add article with marks to list of article headers we want
> to fetch. (dolist (arts (gnus-info-marks (gnus-get-info
> group))) (setq articles (gnus-range-add articles (cdr
> arts)))) (setq articles (sort (gnus-uncompress-sequence
> articles) '<))
Ouch, yes. That code was added, because that if the articles are
not fetched into the agent, when entering the group Gnus will
notice that certain articles doesn't exists and remove the mark.
So to kludge around that, the agent fetches all articles with
marks (which could be useful anyway). But it surely isn't useful
with `seen' and `recent'.
I'm not sure what a good solution would be though.
next prev parent reply other threads:[~2002-01-20 11:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 20:22 Steinar Bang
2002-01-02 0:16 ` Lars Magne Ingebrigtsen
2002-01-02 16:34 ` Steinar Bang
2002-01-04 17:41 ` Lars Magne Ingebrigtsen
2002-01-04 22:02 ` Steinar Bang
2002-01-05 5:24 ` Lars Magne Ingebrigtsen
2002-01-05 16:31 ` Steinar Bang
2002-01-05 16:58 ` Lars Magne Ingebrigtsen
2002-01-05 21:07 ` Steinar Bang
2002-01-05 22:26 ` Bjørn Mork
2002-01-06 15:16 ` Steinar Bang
2002-01-19 19:54 ` Lars Magne Ingebrigtsen
2002-01-19 20:19 ` Bjørn Mork
2002-01-19 20:30 ` Lars Magne Ingebrigtsen
2002-01-19 20:59 ` Bjørn Mork
2002-01-19 21:07 ` Lars Magne Ingebrigtsen
2002-01-20 6:14 ` Bjørn Mork
2002-01-20 11:11 ` Simon Josefsson [this message]
2002-01-20 15:32 ` Lars Magne Ingebrigtsen
2002-01-20 17:12 ` Simon Josefsson
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=ilur8oluvj2.fsf@extundo.com \
--to=jas@extundo.com \
--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).