Re: Agent gone mad?

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

Henrik Enberg <henrik@enberg.org> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> Henrik Enberg <henrik@enberg.org> writes:
>>
>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>>>
>>>> 	(when (<= low high)
>>>> 	  (setq articles (gnus-list-range-intersection
>>>> 			  articles (list (cons low high)))))))
>>>>
>>> Whee, it works when I remove that condition.  Both with
>>> `gnus-agent-consider-all-articles' set to nil and t.  `low' is indeed
>>> higher than `high' for my groups. 
>>
>> Fascinating.  What are those values, more precisely?  
>
> Running the below function to mimic the behaviour in the above code, I
> always get "high" as 1 less than "low", so the when clause will never
> be executed.
>
> (defun high/low ()
>   (interactive)
>   (let ((low (1+ (caar (last gnus-agent-article-alist))))
> 	(high (cdr (gnus-active gnus-newsgroup-name))))
>     (message "high = %s, low = %s" high low)))

Gah?

>> I found that (gnus-list-range-intersection '(1 2 3 4 5) '((5 . 4)))
>> evals to nil, for instance.  So when low > high, no articles were
>> downloaded in my case.  What happens when you eval that expression?
>> If you get non-nil, then something is fishy in Gnus.
>
> I also get nil when I eval that.

Okay, so to summarize: when you remove the when condition, Gnus is
quick again.

But that's because it retrieves no articles, because
gnus-list-range-intersection returns nil.

So I'm not sure it's a good idea to remove the condition.


But I don't believe you were happy with the previous agent behavior
if it never retrieved any articles.  So how about you go back to the
gnus-agent version before my messing around with it and see if that
retrieves any articles at all, and also examine the situation in the
code we're talking about.

Maybe I did something wrong when changing the code.

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)