Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Infinite loop in shr.el
Date: Mon, 25 Feb 2013 11:37:00 +0900	[thread overview]
Message-ID: <b4mppzpf7ar.fsf@jpl.org> (raw)
In-Reply-To: <87fw0lkjbv.fsf@topper.koldfront.dk>

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

Adam Sjøgren wrote:
> Have you got an example you can share?

The attached one might not be the same case but it is really
a menace to shr.  To solve it is easy, though I don't know how
large we should increase max-specpdl-size by default temporarily.


[-- Attachment #2: 53302.gz --]
[-- Type: application/x-gunzip, Size: 6570 bytes --]

[-- Attachment #3: Type: text/plain, Size: 87 bytes --]

This used to be:
http://article.gmane.org/gmane.linux.debian.devel.gnome.general/53302

      reply	other threads:[~2013-02-25  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-23 18:49 Vincent Bernat
2013-02-24 12:05 ` Adam Sjøgren
2013-02-25  2:37   ` Katsumi Yamaoka [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=b4mppzpf7ar.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).