From: Chris Moore <christopher.ian.moore@gmail.com>
Cc: emacs-pretest-bug@gnu.org, Chong Yidong <cyd@stupidchicken.com>,
christopher.ian.moore@gmail.com, ding@gnus.org
Subject: Re: gnus crashes on threads deeper than 333 articles
Date: Mon, 04 Dec 2006 17:37:54 +0100 [thread overview]
Message-ID: <m2d56z39ct.fsf@chrislap.local> (raw)
In-Reply-To: <E1GrEhV-0005u2-QL@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> That change is needed, and not too big.
> If it works, please install it.
I don't think it does work quite right.
I've tried opening the mailbox with the long thread and it still
doesn't work. I get a different error now though:
Debugger entered--Lisp error: (args-out-of-range ["" " " " " " " " " " " "
aref(["" " " " " " " " " " " " " "
(setq gnus-tmp-indentation (aref gnus-thread-indent-array gnus-tmp-level) gnus-tmp-lines (mail-header-lines gnus-tmp-header) gnu
(progn (when (and gnus-tmp-dummy-line ...) (gnus-summary-insert-dummy-line gnus-tmp-dummy-line ...) (setq gnus-tmp-dummy-line ni
(if gnus-tmp-header (progn (when ... ... ...) (setq gnus-tmp-unread ...) (push ... gnus-newsgroup-data) (setq gnus-tmp-subject-o
(when gnus-tmp-header (when (and gnus-tmp-dummy-line ...) (gnus-summary-insert-dummy-line gnus-tmp-dummy-line ...) (setq gnus-tm
(if (stringp gnus-tmp-header) (cond (... ... ... ... ...) (... ... ...) (... ... ...) (t ...)) (setq number (mail-header-number
(while (or threads stack gnus-tmp-new-adopts new-roots) (if (and ... ... ... ...) (if gnus-tmp-new-adopts ... ...) (if threads .
(if (vectorp (car threads)) (gnus-summary-prepare-unthreaded threads) (if gnus-summary-display-while-building (switch-to-buffer
(let ((gnus-tmp-level 0) (default-score ...) (gnus-visual-p ...) (building-line-count gnus-summary-display-while-building) (buil
gnus-summary-prepare-threads((("[CaravelNet (Forum Games)] Re: Guess the Screenshot!" ([53 "[CaravelNet (Forum Games)] Re: Guess
(progn (gnus-summary-prepare-threads (if gnus-show-threads ... ...)))
(if gnus-newsgroup-headers (progn (gnus-summary-prepare-threads ...)))
(when gnus-newsgroup-headers (gnus-summary-prepare-threads (if gnus-show-threads ... ...)))
(let ((buffer-read-only nil)) (erase-buffer) (setq gnus-newsgroup-data nil gnus-newsgroup-data-reverse nil) (gnus-run-hooks (quo
gnus-summary-prepare()
(if no-display nil (gnus-summary-prepare))
(unless no-display (gnus-summary-prepare))
(cond ((not new-group) (gnus-set-global-variables) (when kill-buffer ...) (gnus-configure-windows ... ...) (gnus-set-mode-line .
(let* ((new-group ...) (quit-config ...) (did-select ...)) (cond (... ... ... ... ... ... ... t) (... ... ... nil) (... ... ...
gnus-summary-read-group-1("fun.drod" t nil nil nil nil)
(or (gnus-summary-read-group-1 group show-all no-article kill-buffer no-display select-articles) (setq show-all nil select-artic
(let ((gnus-auto-select-next nil)) (or (gnus-summary-read-group-1 group show-all no-article kill-buffer no-display select-articl
(setq result (let (...) (or ... ...)))
(null (setq result (let ... ...)))
(and group (null (setq result ...)) (eq gnus-auto-select-next (quote quietly)))
(while (and group (null ...) (eq gnus-auto-select-next ...)) (set-buffer gnus-group-buffer) (when backward (gnus-group-prev-unre
(let (result) (while (and group ... ...) (set-buffer gnus-group-buffer) (when backward ...) (if ... ... ...)) result)
gnus-summary-read-group("fun.drod" t nil nil nil nil nil)
gnus-group-read-group(nil nil "fun.drod")
gnus-fetch-group("fun.drod")
call-interactively(gnus-fetch-group)
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
ELISP> before-sorting
*** IELM Error *** Error during pretty-printing (bug in pp)
ELISP> (print before-sorting)
*** Eval error *** Apparently circular structure being printed
ELISP> (prin1 before-sorting)
*** Eval error *** Apparently circular structure being printed
ELISP> print-circle
nil
ELISP> (setq print-circle t)
t
ELISP> before-sorting
*** IELM Error *** Error during pretty-printing (bug in pp)
ELISP> (print before-sorting)
*** Eval error *** Apparently circular structure being printed
ELISP>
but I'm not able to work out how to view the list, due to "bug in pp"
and "apparently circular structure" errors.
next prev parent reply other threads:[~2006-12-04 16:37 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 [this message]
2006-12-04 16:59 ` Chris Moore
2006-12-04 18:35 ` Chris Moore
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=m2d56z39ct.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).