Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: FIXED: Problem quitting a group (current CVS)
Date: Thu, 22 Jan 2004 07:30:42 -0500	[thread overview]
Message-ID: <uy8s0dv2l.fsf_-_@xpediantsolutions.com> (raw)
In-Reply-To: <yovay8s0gsir.fsf@relaskop.wsl.ch>

Adrian Lanz <lanz@fowi.ethz.ch> writes:

> The same here.
>
> In the messsage buffer I see:
>
> Exiting summary buffer and applying spam rules
> Registering 0  articles with classification spam, check spam-use-bogofilter
> Registering 0  articles with classification spam, check spam-use-blacklist
> (No changes need to be saved) [2 times]
> Marking spam as expired without moving it
> Moving ham messages from spam group
> Entering debugger...
>
> ... and then the debugger information:
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>   gnus-compress-sequence((nil) t)
>   gnus-update-marks()
>   gnus-summary-update-info()
>   gnus-summary-expire-articles()
>   run-hooks(gnus-summary-prepare-exit-hook)
>   apply(run-hooks gnus-summary-prepare-exit-hook)
>   gnus-run-hooks(gnus-summary-prepare-exit-hook)
>   gnus-summary-exit()
>   call-interactively(gnus-summary-exit)
>
>
> Thanks, Adrian

Sorry about that.  I was certain that I tested the boundary conditions
but still missed one.  Checkout the lastest gnus-sum.el to get the
patch.

Kevin



  reply	other threads:[~2004-01-22 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22  8:59 Norbert Koch
2004-01-22 10:57 ` Adrian Lanz
2004-01-22 12:30   ` Kevin Greiner [this message]
2004-01-22 12:48     ` FIXED: " 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=uy8s0dv2l.fsf_-_@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).