From: Chris Moore <christopher.ian.moore@gmail.com>
Cc: emacs-pretest-bug@gnu.org, Chong Yidong <cyd@stupidchicken.com>,
ding@gnus.org
Subject: Re: gnus crashes on threads deeper than 333 articles
Date: Mon, 04 Dec 2006 19:35:30 +0100 [thread overview]
Message-ID: <m21wnfv79p.fsf@chrislap.local> (raw)
In-Reply-To: <m27ix7r40h.fsf@chrislap.local>
Chris Moore <christopher.ian.moore@gmail.com> writes:
> Chris Moore <christopher.ian.moore@gmail.com> writes:
>
>> One thing I noticed it that the new sort funcction changes the length
>> of the list of threads:
>>
>> *** Welcome to IELM *** Type (describe-mode) for help.
>> ELISP> (length before-sorting)
>> 106
>> ELISP> (length after-sorting)
>> 258
>
> That seems to be a red herring. Running the new sort function on
> before-sorting gives a list the same length as running the old sort
> function does. I tried using 'equal to compare the 2 outputs, but got
> a stack overflow error.
OK, so the 'loop' version of the sort function does seem to work, but
fixing that has shown up a new problem.
The '200' and '201' in this function limit the thread depth.
Increasing these numbers has allowed me to finally open my large
Increasing these mailbox!
(defun gnus-make-thread-indent-array ()
(let ((n 200))
(unless (and gnus-thread-indent-array
(= gnus-thread-indent-level gnus-thread-indent-array-level))
(setq gnus-thread-indent-array (make-vector 201 "")
next prev parent reply other threads:[~2006-12-04 18:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Gpndn-0003Wt-Dq@chrislap.local>
2006-12-03 20:36 ` Chong Yidong
2006-12-04 14:21 ` Richard Stallman
2006-12-04 16:37 ` Chris Moore
2006-12-04 16:59 ` Chris Moore
2006-12-04 18:35 ` Chris Moore [this message]
2006-12-04 18:58 ` Reiner Steib
2006-12-04 19:51 ` Chris Moore
2006-12-04 16:05 ` Reiner Steib
2006-12-04 19:05 ` Chong Yidong
2006-12-05 5:09 ` Richard Stallman
2006-12-05 9:29 ` Reiner Steib
2006-12-06 0:47 ` Richard Stallman
2006-12-05 16:52 ` Chong Yidong
2006-12-05 16:59 ` Chong Yidong
2006-12-05 18:59 ` Chris Moore
2006-12-07 16:29 ` Chong Yidong
2006-12-05 17:02 ` Chris Moore
2006-12-05 17:05 ` Chong Yidong
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=m21wnfv79p.fsf@chrislap.local \
--to=christopher.ian.moore@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.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).