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 16:27:39 +0200 [thread overview]
Message-ID: <874ko169b8.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87o8m9oj1f.fsf@ust.hk>
Andrew writes:
> 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.
Ok.
> Can you remove the notmuch search engine declaration just from your
> archive backend temporarily, and then try a variety of searches?
I still get the error when q'ing the search for Natas Kaupas when I have
removed the declaration from the archive backend.
(If my vague theory that a hit in ~/Mail/archive/ should be interpreted
as a hit in nnml+archive: but is interpreted as a hit in nnml:archive.
is correct, this is what we'd expect to see, right?
I just don't see how Gnus could automatically interpret
~/Mail/archive/mail-2020/NNNN "correctly", i.e. as
nnml+archive:mail-2020/NNNN and not nnml:archive.mail-2020/NNNN...)
> 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.
The backtrace is:
Debugger entered--Lisp error: (args-out-of-range [["nnml:archive.mail-2020" 438 0]] 999)
nnselect-article-group(1000)
#f(compiled-function (member) #<bytecode 0x1867c218cbfaae5d>)(1000)
mapc(#f(compiled-function (member) #<bytecode 0x1867c218cbfaae5d>) (1000 999 998 997 996 995 994 993 992 991 990 989 988 987 986 985 984 983 982 981 980 979 978 977 976 975 974 973 972 971 970 969 968 967 966 965 964 963 962 961 960 959 958 957 956 955 954 953 952 951 ...))
nnselect-push-info("nnselect:nnselect-875z8h69ea.fsf")
nnselect-close-group("nnselect-875z8h69ea.fsf" "nnselect-ephemeral")
gnus-close-group("nnselect:nnselect-875z8h69ea.fsf")
gnus-summary-exit()
funcall-interactively(gnus-summary-exit)
call-interactively(gnus-summary-exit nil nil)
command-execute(gnus-summary-exit)
Best regards,
Adam
--
"I mean, what a disappointing 21st century this has Adam Sjøgren
been so far, you know?" asjo@koldfront.dk
next prev parent reply other threads:[~2020-09-13 14:28 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 [this message]
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=874ko169b8.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).