From: Karl Kleinpaste <karl@charcoal.com>
Subject: Exiting a group with (all?) expiring articles is currently broken
Date: Thu, 30 Aug 2001 21:35:13 -0400 [thread overview]
Message-ID: <vxkd75droz2.fsf@cinnamon.vanillaknot.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
I have an nnml group "tomb" where spam goes to die. It has these
properties:
[-- Attachment #2: tomb properties --]
[-- Type: text/plain, Size: 61 bytes --]
((banner . egroups)
(total-expire . t)
(expiry-wait . 0))
[-- Attachment #3: Type: text/plain, Size: 148 bytes --]
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:
[-- Attachment #4: tomb exit trace --]
[-- Type: text/plain, Size: 974 bytes --]
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)
[-- Attachment #5: Type: text/plain, Size: 230 bytes --]
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'.
next reply other threads:[~2001-08-31 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 1:35 Karl Kleinpaste [this message]
2001-08-31 18:01 ` Henrik Enberg
2001-08-31 19:04 ` Karl Kleinpaste
2001-08-31 19:15 ` Karl Kleinpaste
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=vxkd75droz2.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).