From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/38453
Path: main.gmane.org!not-for-mail
From: Karl Kleinpaste <karl@charcoal.com>
Newsgroups: gmane.emacs.gnus.general
Subject: Exiting a group with (all?) expiring articles is currently broken
Date: Thu, 30 Aug 2001 21:35:13 -0400
Message-ID: <vxkd75droz2.fsf@cinnamon.vanillaknot.com>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
X-Trace: main.gmane.org 1035174314 22524 80.91.224.250 (21 Oct 2002 04:25:14 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Mon, 21 Oct 2002 04:25:14 +0000 (UTC)
Keywords: tomb,properties,group,exit
Return-Path: <karl@charcoal.com>
Return-Path: <karl@charcoal.com>
Original-Received: (qmail 6051 invoked from network); 31 Aug 2001 01:35:09 -0000
Original-Received: from mesquite.slip.cs.cmu.edu (HELO cinnamon.vanillaknot.com) (128.2.207.11)
  by gnus.org with SMTP; 31 Aug 2001 01:35:09 -0000
Original-Received: (from karl@localhost)
	by cinnamon.vanillaknot.com (8.11.2/8.11.2) id f7V1ZDQ17667;
	Thu, 30 Aug 2001 21:35:13 -0400
Original-To: ding@gnus.org
X-Face: ?=p^Gj2JkX~UU_@W}[q/'Dxn19x-zfIQ](y<&ky/?1-&Nz&,!W}R.Gp+"LeGojoR
	=RF>?!XVs{a:`Yt(gqM<#$Zy(C@]'dR4Hy4S1.I(n3:2"R:=Uy!)K9>U!gNTyH{p
	+_w#F[gt).$Vyvo5=9LF^PeQ(@H#}QLAbfyYxX/8t:TDR5nA\|RmJO"EwjL8tWyvM
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Artificial
 Intelligence)
Original-Lines: 15
Xref: main.gmane.org gmane.emacs.gnus.general:38453
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:38453

--=-=-=

I have an nnml group "tomb" where spam goes to die.  It has these
properties:


--=-=-=
Content-Disposition: inline; filename=properties
Content-Description: tomb properties

((banner . egroups)
 (total-expire . t)
 (expiry-wait . 0))


--=-=-=

As of a CVS update of about 20 minutes ago (this is Thursday evening,
9:30pm EDT), attempting to exit this group rewards me with this stack
trace:


--=-=-=
Content-Disposition: inline; filename=stck
Content-Description: tomb exit trace

Signaling: (wrong-type-argument number-char-or-marker-p >)
  <(> 8736)
  sort((8740) <)
  nnml-request-expire-articles((8736 8737 8738 8739 8740) "tomb" "" nil)
  gnus-request-expire-articles((8736 8737 8738 8739 8740) "tomb")
  gnus-summary-expire-articles()
  run-hooks(gnus-summary-expire-articles)
  apply(run-hooks gnus-summary-expire-articles)
  gnus-run-hooks(gnus-summary-prepare-exit-hook)
  gnus-summary-exit(t)
  gnus-summary-next-group(nil "archive.current.personal.slaves" nil)
  gnus-summary-next-article(t "$2000 Weekly Possible Stuffing Envelopes at Home!!")
  #<compiled-function nil "...(73)" [gnus-newsgroup-data gnus-auto-select-same gnus-summary-goto-unread headers to gnus-summary-next-article never gnus-summary-last-article-p get-text-property gnus-intangible gnus-summary-goto-subject gnus-number gnus-summary-last-subject 3 vectorp 1] 7 ("/home/karl/Emacs/Gnus/gnus-sum.elc" . 179250) nil>()
  call-interactively(gnus-summary-next-unread-article)


--=-=-=

The articles are not deleted, though enough internal updating has
occurred that I can force exit with `Q' and find that the articles are
considered to have been read.  That is, the *Group* buffer shows `0'
after exiting with `Q'.

--=-=-=--