Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Cohen <acohen@ust.hk>
To: ding@gnus.org
Subject: Re: Args out of range when quitting search buffer with recent Emacs/Gnus
Date: Sun, 13 Sep 2020 21:53:19 +0800	[thread overview]
Message-ID: <87tuw1oka8.fsf@ust.hk> (raw)
In-Reply-To: <871rj5es8v.fsf@tullinup.koldfront.dk>


>>>>> "AS" == Adam Sjøgren <asjo@koldfront.dk> writes:

[...]

    AS> This is what I did orginally, but I'll do it again. This time I
    AS> did exactly what you wrote, put point on nnml:normal and G G
    AS> query RET.

    AS> q immediately gave this message:

    AS>   Args out of range: [["nnml:ferie" 25 0] ["nnml:never-sent" 10
    AS> 0] ["nnml:never-sent" 72 0] ["nnml:never-sent" 85 0]
    AS> ["nnml:never-sent" 88 0] ["nnml:never-sent" 118 0] ["nnml:dde" 8
    AS> 0] ["nnml:archive.mail-1997" 158 0] ["nnml:archive.mail-1997"
    AS> 164 0] ["nnml:lasseoe" 51 0] ...], 999

    AS> I have my normal email in ~/Mail and archive email in
    AS> ~/Mail/archive, and notmuch indexes both in one index - it looks
    AS> like the hits in ~/Mail/archive are assigned a dot-group in
    AS> nnml: rather than a group in nnml+archive: - might that be
    AS> causing the problem?

I think this is expected (but I don't use notmuch so I'm not
positive). I think that gnus refers to the groups in your directory
hierarchy with dots rather than slashes, so these group names should be
what gnus wants to retrieve articles in these groups. 

I suspect there are two different things going on (as you say). The
absence of articles in the search on an archive group was probably true
before these changes. The args our of range is new.

If you are still up for some trial and error:

Try to do a search that has only a few hits to keep things
manageable. After doing the search check the value of the variable
'gnus-newsgroup-selection while in the summary buffer. Then see if you
can view any of the articles. Let me know the results and we can go from
there. You might want to send the info privately by email in case you
are concerned about this info revealing anything sensitive.




  reply	other threads:[~2020-09-13 13:54 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 [this message]
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
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=87tuw1oka8.fsf@ust.hk \
    --to=acohen@ust.hk \
    --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).