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 23:51:03 +0800 [thread overview]
Message-ID: <87k0wxoeu0.fsf@ust.hk> (raw)
In-Reply-To: <874ko169b8.fsf@tullinup.koldfront.dk>
>>>>> "AS" == Adam Sjøgren <asjo@koldfront.dk> writes:
[...]
AS> I still get the error when q'ing the search for Natas Kaupas
AS> when I have removed the declaration from the archive backend.
AS> (If my vague theory that a hit in ~/Mail/archive/ should be
AS> interpreted as a hit in nnml+archive: but is interpreted as a
AS> hit in nnml:archive. is correct, this is what we'd expect to
AS> see, right?
AS> I just don't see how Gnus could automatically interpret
AS> ~/Mail/archive/mail-2020/NNNN "correctly", i.e. as
AS> nnml+archive:mail-2020/NNNN and not
AS> nnml:archive.mail-2020/NNNN...)
OK, I had forgotten how nnml works :) I think you are likely right that
gnus can't figure out which backend to assign directories in the same
nnml tree. I guess the simplest thing to try is to move the archive
backend to an orthogonal directory tree.
[...]
AS> The backtrace is:
AS> Debugger entered--Lisp error: (args-out-of-range
AS> [["nnml:archive.mail-2020" 438 0]] 999)
AS> nnselect-article-group(1000) #f(compiled-function (member)
AS> #<bytecode 0x1867c218cbfaae5d>)(1000) mapc(#f(compiled-function
AS> (member) #<bytecode 0x1867c218cbfaae5d>) (1000 999 998 997 996
AS> 995 994 993 992 991 990 989 988 987 986 985 984 983 982 981 980
AS> 979 978 977 976 975 974 973 972 971 970 969 968 967 966 965 964
AS> 963 962 961 960 959 958 957 956 955 954 953 952 951 ...))
AS> nnselect-push-info("nnselect:nnselect-875z8h69ea.fsf")
AS> nnselect-close-group("nnselect-875z8h69ea.fsf"
AS> "nnselect-ephemeral")
AS> gnus-close-group("nnselect:nnselect-875z8h69ea.fsf")
AS> gnus-summary-exit() funcall-interactively(gnus-summary-exit)
AS> call-interactively(gnus-summary-exit nil nil)
AS> command-execute(gnus-summary-exit)
OK, this looks crazy: you have a single search hit but somehow there is
a list of 1000 articles?
If you can separate the trees easily, try that and let me know what
happens. Otherwise we will have to step through the function.
next prev parent reply other threads:[~2020-09-13 15:52 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 [this message]
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=87k0wxoeu0.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).