From: pmlists@free.fr (Peter Münster)
To: ding@gnus.org
Subject: Re: sorting: wrong number of arguments
Date: Sat, 22 Jan 2011 21:35:25 +0100 [thread overview]
Message-ID: <87k4hwad82.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: <874o90vkqe.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> pmlists@free.fr (Peter Münster) writes:
>
>> That's what I'd tried, but:
>> "error: Variable binding depth exceeds max-specpdl-size"
>
> Try setting debug-on-error and see where it infloops.
This seems to be the important part of the backtrace:
--8<---------------cut here---------------start------------->8---
display-warning(bytecomp "Variable binding depth exceeds
max-specpdl-size" :error "*Compile-Log*")
byte-compile-log-warning("Variable binding depth exceeds
max-specpdl-size" nil :error)
byte-compile-report-error((error "Variable binding depth exceeds
max-specpdl-size"))
byte-compile((lambda (t1 t2) (or (gnus-group-sort-by-method t1 t2)
(and ... ...))))
gnus-byte-compile((lambda (t1 t2) (or (gnus-group-sort-by-method t1
t2) (and ... ...))))
gnus-make-sort-function((gnus-group-sort-by-real-name (not
gnus-group-sort-by-unread) gnus-group-sort-by-method))
gnus-group-sort-groups((gnus-group-sort-by-real-name (not
gnus-group-sort-by-unread) gnus-group-sort-by-method))
(lambda nil (gnus-group-sort-groups gnus-group-sort-function))()
run-hooks(gnus-group-update-hook)
--8<---------------cut here---------------end--------------->8---
(the whole backtrace is 152 lines)
--
Peter Münster
Contact information: http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2011-01-22 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 15:46 Peter Münster
2011-01-22 3:44 ` Lars Ingebrigtsen
2011-01-22 8:22 ` Peter Münster
2011-01-22 18:09 ` Lars Ingebrigtsen
2011-01-22 18:32 ` Peter Münster
2011-01-22 18:47 ` Lars Ingebrigtsen
2011-01-22 20:35 ` Peter Münster [this message]
2011-01-22 20:37 ` Lars Ingebrigtsen
2011-01-22 20:48 ` Peter Münster
2011-01-22 20:52 ` Lars Ingebrigtsen
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=87k4hwad82.fsf@micropit.couberia.bzh \
--to=pmlists@free.fr \
--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).