Re: Long wait for "Expiring Articles..."

[Lars Ingebrigtsen <larsi@gnus.org>]

"Jason L Tibbitts III" <tibbs@math.uh.edu> writes:

> And, to continue talking to myself, I learned about the debugger and
> stepped into gnus-request-expire-articles.  Turns out this just gets
> called with a nice big list containing the positive integers from 1 to
> 260000 or so.  Which explains why it takes so long to run.  Doesn't
> explain why Gnus seems to not be keeping track of, or asking the server
> for, the actual number of articles in the group which according to
> previous discussion it's supposed to do.

Hm; looking at the code I see that it tries to do unexist handling, so
it "should work".  >"?

If you step through `gnus-summary-expire-articles', what are the values
of `gnus-newsgroup-unexist', and what does `expirable' end up being here?

    (let* ((total (gnus-group-total-expirable-p gnus-newsgroup-name))
	   (expirable
	    (gnus-list-range-difference
	     (if total
		 (progn
		   ;; We need to update the info for
		   ;; this group for `gnus-list-of-read-articles'
		   ;; to give us the right answer.
		   (gnus-run-hooks 'gnus-exit-group-hook)
		   (gnus-summary-update-info)
		   (gnus-list-of-read-articles gnus-newsgroup-name))
	       (setq gnus-newsgroup-expirable
		     (sort gnus-newsgroup-expirable '<)))
	     gnus-newsgroup-unexist))
	   (expiry-wait (if now 'immediate
			  (gnus-group-find-parameter
			   gnus-newsgroup-name 'expiry-wait)))
	   (nnmail-expiry-target
	    (or (gnus-group-find-parameter gnus-newsgroup-name 'expiry-target)
		nnmail-expiry-target))
	   es)
-->   (when expirable


-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/