From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Agent gone mad?
Date: Mon, 21 Oct 2002 21:12:36 +0200 [thread overview]
Message-ID: <84r8ej7gij.fsf@crybaby.cs.uni-dortmund.de> (raw)
In-Reply-To: <87u1jfadtb.fsf@enberg.org>
Henrik Enberg <henrik@enberg.org> writes:
> Yes, because while it's fast, it also tries to download every article
> my server knows about.
Whee. Hm. This does not happen for me. Otherwise things would be
even slower still.
>> Okay. What's in the 100 megs that it is still downloading? Is it
>> headers or articles or both? I might need to meditate a lot more
>> about that code...
>
> It is both headers and articles. Even those already downloaded. It
> seems to just throw away what it downloads.
Really really strange. How could that happen? Can you trace the
code (with edebug?) to see what happens?
>> Btw, I've now reinstated another change of mine which abstains from
>> fetching already-fetched messages. Maybe that helps some more.
>
> There are some changes in the behaviour. With
> `gnus-agent-consider-all-articles' set to nil, it still does what I
> described above. If I set it to t, Gnus just locks up until I hit C-g.
>
> I've been staring at the code for quite some time, but I don't
> understand why it doesn't work. It is clearly conditioned on
> gnus-agent-consider-all-articles. It really _ought_ to work.
Well, the code that's conditioned on gnus-agent-consider-all-articles
only influences the header fetching. Hm.
There is one spot which I changed:
;; Remove known articles.
(when (gnus-agent-load-alist group)
;; Remove articles marked as downloaded.
(setq articles
(gnus-sorted-difference
articles
(delq nil
(mapcar (lambda (x) (when (cdr x) (car x)))
gnus-agent-article-alist))))
(let ((low (1+ (caar (last gnus-agent-article-alist))))
(high (cdr (gnus-active group))))
;; I suspect a deeper problem here and I suspect that low
;; should never be greater than high. But for the time being
;; we just work around the problem and abstain from frobbing
;; the article list in that case. If anyone knows how to
;; properly deal with it, please holler. -- kai
(when (<= low high)
(setq articles (gnus-list-range-intersection
articles (list (cons low high)))))))
The last `when' was not there originally. For me, low was greater
than high and therefore gnus-list-range-intersection returned nil.
But maybe for you low is also greater than high but
gnus-list-range-intersection does not return nil?
How about you try to remove that (<= low high) condition and see what
happens?
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-21 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 20:55 Henrik Enberg
2002-10-19 21:01 ` Henrik Enberg
2002-10-20 16:35 ` Kai Großjohann
2002-10-21 0:12 ` Henrik Enberg
2002-10-20 19:42 ` Kai Großjohann
2002-10-21 0:15 ` Henrik Enberg
2002-10-21 6:42 ` Kai Großjohann
2002-10-21 17:42 ` Henrik Enberg
2002-10-21 19:12 ` Kai Großjohann [this message]
2002-10-21 19:32 ` Henrik Enberg
2002-10-22 5:50 ` Kai Großjohann
2002-10-22 19:10 ` Henrik Enberg
2002-10-22 20:07 ` Kai Großjohann
2002-10-22 20:37 ` Henrik Enberg
2002-10-23 6:11 ` Kai Großjohann
2002-10-22 9:48 ` Simon Josefsson
2002-10-22 10:02 ` 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=84r8ej7gij.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).