From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 13802@debbugs.gnu.org
Subject: bug#13802: stack overflow in mm-add-meta-html-tag
Date: Fri, 31 Jan 2014 07:10:28 +0100 [thread overview]
Message-ID: <8761p0d6ln.fsf@zigzag.favinet> (raw)
In-Reply-To: <8761p17zom.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Thu, 30 Jan 2014 16:38:49 -0800")
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
() Lars Ingebrigtsen <larsi@gnus.org>
() Thu, 30 Jan 2014 16:38:49 -0800
Juri Linkov <juri@jurta.org> writes:
> `sgml-html-meta-auto-coding-function' uses a similar regexp that
> doesn't fail with stack overflow. You could get some ideas from
> this regexp and sync the regexp in `mm-add-meta-html-tag' with it.
I've adapted the regexp from that function in the patch below, but
since I don't have a test case, I'm not really sure about committing
it.
Thien-Thi, could you post the message that triggers this error, or
the relevant bits of it?
I'd like to, but no longer have immediate access to that particular
message -- it might take a day or two to excavate (if at all). However,
i do remember it was all on one line (no newlines, machine generated).
diff [...]
- ORIGINAL-HAIRY-REGEXP
+ ANOTER-HAIRY-REGEXP
Maybe this would be a good time to substitute a symbolic regexp?
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-01-31 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 9:17 bug#13802: stack overflow in mm-add-meta-html-tag Thien-Thi Nguyen
2013-02-25 0:20 ` Juri Linkov
2014-01-31 0:38 ` Lars Ingebrigtsen
2014-01-31 6:10 ` Thien-Thi Nguyen [this message]
2016-03-01 5:58 ` Lars Ingebrigtsen
2013-02-25 2:04 ` Stefan Monnier
2013-07-06 16:11 ` 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=8761p0d6ln.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=13802@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.