From: Norbert Koch <viteno@xemacs.org>
Subject: Problem quitting a group (current CVS)
Date: Thu, 22 Jan 2004 09:59:11 +0100 [thread overview]
Message-ID: <vzr7xsmk9s.fsf@redqueen.bytechase.cx> (raw)
Hi!
No Gnus v0.2
21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid
When I quit a group, in some cases I get the following error:
Signaling: (wrong-type-argument number-char-or-marker-p nil)
gnus-compress-sequence((nil) t)
gnus-update-marks()
gnus-summary-update-info()
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)
#<compiled-function (&optional temporary leave-hidden) "...(434)" [gnus-article-buffer group gnus-buffers quit-config buffer buf gnus-set-global-variables gnus-buffer-live-p mm-destroy-parts nil gnus-kill-save-kill-buffer gnus-async-halt-prefetch gnus-group-quit-config t gnus-score-adaptive gnus-score-save gnus-run-hooks gnus-summary-prepare-exit-hook get-buffer buffer-name delete kill-buffer gnus-cache-possibly-remove-articles gnus-cache-save-buffers gnus-async-prefetch-remove-group gnus-dup-enter-articles gnus-tree-close gnus-cache-write-active nnmail-purge-split-history string-match "^[^:]+:" 0 gnus-exit-group-hook gnus-summary-update-info gnus-close-group gnus-group-jump-to-group gnus-summary-exit-hook gnus-group-group-name gnus-group-next-unread-group 1 gnus-deaden-summary gnus-summary-clear-local-variables bury-buffer gnus-summary-mode pop-to-buffer gnus-configure-windows force gnus-handle-ephemeral-exit gname gnus-group-buffer ...] 5 ("/usr/users/nk/local/lib/xemacs/site-packages/lisp/gnus/gnus-sum.elc" . 185560) nil>()
call-interactively(gnus-summary-exit)
norbert.
next reply other threads:[~2004-01-22 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 8:59 Norbert Koch [this message]
2004-01-22 10:57 ` Adrian Lanz
2004-01-22 12:30 ` FIXED: " Kevin Greiner
2004-01-22 12:48 ` Norbert Koch
2004-01-22 15:43 ` Adrian Lanz
2004-01-23 2:30 ` Kevin Greiner
2004-01-23 7:30 ` Norbert Koch
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=vzr7xsmk9s.fsf@redqueen.bytechase.cx \
--to=viteno@xemacs.org \
/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).