Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Args out of range when quitting search buffer with recent Emacs/Gnus
Date: Sun, 13 Sep 2020 21:45:46 +0200	[thread overview]
Message-ID: <87wo0xe9zp.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87imchscib.fsf@ericabrahamsen.net>

Eric writes:

> I think the simplest next step would be to figure out which list of
> marks thinks there are 1000 articles in this group. Is it always 1000,
> no matter how many search results you get?

It seems to be, when I get the error.

> Would you run a search that you're confident will trigger the error, and
> evaluate this *in that buffer* (ie with "M-:" in the buffer).
>
> (setq length-pairs
>       (mapcar (lambda (mark-list)
> 		(cons mark-list
> 		      (length (symbol-value mark-list))))
> 	      (append (mapcar
> 		       (lambda (type)
> 			 (intern (format "gnus-newsgroup-%s" (car type))))
> 		       gnus-article-mark-lists)
> 		       '(gnus-newsgroup-unreads gnus-newsgroup-unseen))))
>
> And then show us the (expanded) value of `length-pairs'?

Is this what you're after:

  length-pairs’s value is shown below.

  Documentation:
  Not documented as a variable.

  Value:
  ((gnus-newsgroup-marked . 0)
   (gnus-newsgroup-replied . 2)
   (gnus-newsgroup-expirable . 0)
   (gnus-newsgroup-killed . 0)
   (gnus-newsgroup-bookmarks . 0)
   (gnus-newsgroup-dormant . 0)
   (gnus-newsgroup-scored . 8)
   (gnus-newsgroup-saved . 0)
   (gnus-newsgroup-cached . 0)
   (gnus-newsgroup-downloadable . 0)
   (gnus-newsgroup-unsendable . 0)
   (gnus-newsgroup-forwarded . 0)
   (gnus-newsgroup-seen . 3)
   (gnus-newsgroup-unexist . 0)
   (gnus-newsgroup-unreads . 0)
   (gnus-newsgroup-unseen . 2))

?

The search for USB ID on nnml:normal returned a group with 94 articles
in it. Trying to q gave the usual:

  Args out of range: [["nnml:cvs" 1664 0] ["nnml:cvs" 1667 0] ["nnml:rt2400-devel" 74 0] ["nnml:rt2400-devel" 75 0] ["nnml:never-sent" 43 0] ["nnml:debian-bts" 225 0] ["nnml:debian-bts" 228 0] ["nnml:leif" 2036 0] ["nnml:cron" 6244 0] ["nnml:cron" 17494 0] ...], 999

error.


  Best regards,

    Adam

-- 
 "Few things are less comforting than a tiger who's         Adam Sjøgren
  up too late."                                        asjo@koldfront.dk



  reply	other threads:[~2020-09-13 19:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12 18:53 Adam Sjøgren
2020-09-13 12:43 ` Andrew Cohen
2020-09-13 13:11   ` Adam Sjøgren
2020-09-13 13:53     ` Andrew Cohen
2020-09-13 14:06       ` Adam Sjøgren
2020-09-13 14:20         ` Andrew Cohen
2020-09-13 14:27           ` Adam Sjøgren
2020-09-13 15:51             ` Andrew Cohen
2020-09-13 16:13               ` Adam Sjøgren
2020-09-13 19:27                 ` Eric Abrahamsen
2020-09-13 19:45                   ` Adam Sjøgren [this message]
2020-09-13 20:26                     ` Eric Abrahamsen
2020-09-13 20:46                       ` Adam Sjøgren
2020-09-13 21:01                         ` Eric Abrahamsen
2020-09-13 23:30                           ` Andrew Cohen
2020-09-13 23:48                             ` Andrew Cohen
2020-09-14 16:02                               ` Adam Sjøgren
2020-09-14 20:28                                 ` Eric Abrahamsen
2020-09-14 23:27                                   ` Andrew Cohen
2020-09-14 15:47                             ` Adam Sjøgren
2020-09-13 16:48         ` Eric Abrahamsen

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=87wo0xe9zp.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=ding@gnus.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).