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 22:20:12 +0800	[thread overview]
Message-ID: <87o8m9oj1f.fsf@ust.hk> (raw)
In-Reply-To: <87r1r5db4n.fsf@tullinup.koldfront.dk>


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

[...]


    AS> Ok, I go to nnml:normal in the group buffer and G G
    AS> ejendomsvurderingen RET - this gives 2 hits, both in
    AS> nnml:normal, and q works!

    AS> And I can see both articles.

    AS> Hm.

    AS> Does the problem only appear when I get hits in archive/ ?

    AS> It seems so:

    AS> If I go G G Natas Kaupas RET, I get 1 hit, which is in
    AS> archive/mail-2020. I can see the article, but when I q the
    AS> search buffer, I get:

    AS>   Args out of range: [["nnml:archive.mail-2020" 438 0]], 999


[...]

    AS> Should I move my archive so it isn't "colocated" with my normal
    AS> emails, or should Gnus handle this odd cornercase?

I don't think there should be anything wrong your setup, so we should
try to get gnus to not fail. I am going to have to go to bed soon, but
if you can try one more thing to nail this down. Can you remove the
notmuch search engine declaration just from your archive backend temporarily,
and then try a variety of searches? I want to make sure the problem is
really associated with the archive group. After this you can re-enable
the search engine for the archive backend.

I guess the next step is to do some debugging. Since we have a nice
failure case ("Natas Kaupas")  this shouldn't be too bad. Try setting
debug-on-error and get a backtrace so we know where the failure is. Then
we can try debugging that function to get a better idea of what is
happening.

Best,
Andy



  reply	other threads:[~2020-09-13 14:20 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 [this message]
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=87o8m9oj1f.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).