From: Knut Anders Hatlen <kahatlen@gmail.com>
To: ding@gnus.org
Subject: Re: shr fails to display article (exceeds max-lisp-eval-depth)
Date: Sat, 06 Nov 2010 18:37:15 +0100 [thread overview]
Message-ID: <x6wroq1hh0.fsf@gmail.com> (raw)
In-Reply-To: <x61v6y2wc7.fsf@gmail.com>
Knut Anders Hatlen <kahatlen@gmail.com> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Knut Anders Hatlen <kahatlen@gmail.com> writes:
>>
>>> I just got this spam mail that shr choked on. I know, I shouldn't spend
>>> time reading spam, but... shr shouldn't choke either...
>>>
>>> Debugger entered--Lisp error: (error "Lisp nesting exceeds
>>> max-lisp-eval-depth'")
>>> (setq dom (cdr dom))
>>> (prog1 dom (setq dom (cdr dom)))
>>> (car (prog1 dom (setq dom (cdr dom))))
>>
>> Are you running Gnus/shr uncompiled? You can only do that semi-reliably
>> if you double `max-lisp-eval-depth', usually.
>
> Right, shr.el doesn't seem to be compiled, and M-x byte-compile-file
> does indeed fix the problem. Thanks! But shouldn't it be compiled
> automatically when I run `make'?
D'oh! I had compiled Gnus with Emacs 23.2, so of course it didn't
compile shr.el. With Emacs 24 it compiles. Sorry about the noise.
--
Knut Anders
prev parent reply other threads:[~2010-11-06 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 16:54 Knut Anders Hatlen
2010-11-06 17:19 ` Lars Magne Ingebrigtsen
2010-11-06 17:30 ` Knut Anders Hatlen
2010-11-06 17:37 ` Knut Anders Hatlen [this message]
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=x6wroq1hh0.fsf@gmail.com \
--to=kahatlen@gmail.com \
--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).