Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: Re: wrong number of arguments (Re: void-variable deactivate-mark)
Date: Tue, 26 Nov 2002 23:31:27 +0100	[thread overview]
Message-ID: <v91y587ykg.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <84n0nwul4a.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Tue, 26 Nov 2002 21:33:25 +0100")

On Tue, Nov 26 2002, Kai Großjohann wrote:

> Reiner Steib <4uce.02.r.steib@gmx.net> writes:
[...]
>> Sorry, not for me. When I call `/ o' I get the following backtrace:
>
> Hm.  But now gnus-summary-insert-old-articles uses gnus-range-difference
> from Kevin!  Hm.

gnus-summary-insert-old-articles calls gnus-summary-insert-articles
and there is ...

,----[ gnus-sum.el ]
| (defun gnus-summary-insert-articles (articles)
|   (gnus-message 9 "[1] articles: %s" articles) (sit-for 1) ;; Added for
| 							   ;; debugging!
|   (when (setq articles
| 	      (gnus-sorted-difference articles
| 				      (mapcar (lambda (h)
| 						(mail-header-number h))
| 					      gnus-newsgroup-headers)))
|     (gnus-message 9 "[2] articles: %s" articles) (sit-for 1) ;; Added for
| 							     ;; debugging!
`----

,----[ *Messages* ]
| [1] articles: ((9240 . 9565) (9567 . 9573) (9575 . 9595) (9597 .
| 9600) 9602 (9606 . 9607))
| setq: Wrong type argument: number-or-marker-p, (9240 . 9565)
`----

I don't grok that code, but it seems there's some mismatch in the
arguments (`articles' argument passed to gnus-summary-insert-article
from gnus-summary-insert-old-articles).

> I just tried `10 / o' and that worked well.

That's fine for me too. `111111 / o' too. Could you (or someone else)
try `/ o' without any prefix argument?

> And `/ o 10 RET' also works.

I don't understand this (maybe I'm too tired): `10 RET' after `/ o'?
Gives me the backtrace immediately after `/ o'

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/



  reply	other threads:[~2002-11-26 22:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 14:56 void-variable deactivate-mark Mats Lidell
2002-11-25 17:50 ` Kai Großjohann
2002-11-26  7:51   ` Norbert Koch
2002-11-26 11:16     ` Kai Großjohann
2002-11-26 11:50       ` Norbert Koch
2002-11-26 11:54       ` Katsumi Yamaoka
2002-11-26 12:08         ` wrong number of arguments (Re: void-variable deactivate-mark) Katsumi Yamaoka
2002-11-26 12:21           ` Kai Großjohann
2002-11-26 12:34             ` Katsumi Yamaoka
2002-11-26 13:52               ` Kai Großjohann
2002-11-26 16:22               ` Kai Großjohann
2002-11-26 17:43             ` Reiner Steib
2002-11-26 18:11               ` Kevin Greiner
2002-11-26 23:06                 ` Reiner Steib
2002-12-02 16:49                   ` David S Goldberg
2002-11-27 18:06                 ` Reiner Steib
2002-11-27 18:57                   ` Kevin Greiner
2002-11-26 20:33               ` Kai Großjohann
2002-11-26 22:31                 ` Reiner Steib [this message]
2002-11-26 23:37                   ` Nevin Kapur
2002-11-27  8:54                     ` Reiner Steib
2002-12-28 20:18 ` void-variable deactivate-mark Lars Magne Ingebrigtsen

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=v91y587ykg.fsf@marauder.physik.uni-ulm.de \
    --to=4uce.02.r.steib@gmx.net \
    --cc=reiner.steib@gmx.de \
    /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).