From: Kevin Ryde <user42@zip.com.au>
To: bug-gnu-emacs@gnu.org
Subject: bug#4512: 23.1; html-mode C-c C-f on runs of <P>
Date: Tue, 22 Sep 2009 08:48:12 +1000 [thread overview]
Message-ID: <87skefhq37.fsf@blah.blah> (raw)
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
In a html-mode buffer with runs of successive <P> tags, like
(progn
(switch-to-buffer "foo")
(dotimes (i 5000) (insert (format "<p> abc\n" i)))
(goto-char (point-min))
(html-mode))
pressing C-c C-f gets an error
Variable binding depth exceeds max-specpdl-size
instead of going forward. The way C-c C-f `sgml-skip-tag-forward'
requires a closing </P> etc is no doubt what's wanted for sgml, but for
the looser html it'd be good if it recognised some closing tags are
optional.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sgml-mode.el.skip-comment.diff --]
[-- Type: text/x-diff, Size: 777 bytes --]
--- sgml-mode.el.~1.140.~ 2009-08-22 07:48:30.000000000 +1000
+++ sgml-mode.el 2009-09-22 08:42:35.000000000 +1000
@@ -840,6 +840,14 @@
;; FIXME: Use sgml-get-context or something similar.
;; It currently might jump to an unrelated </P> if the <P>
;; we're skipping has no matching </P>.
+
+ ;; FIXME: For html-mode a closing </P> is optional, and others like
+ ;; </TR> similarly. This code or some `html-skip-tag-forward'
+ ;; should recognise a new <P> ends a previous <P>, and with some
+ ;; precedence levels among <TR>, <TD>, <P>, etc. Currently the
+ ;; recursion in the `while' below means runs of successive <P> error
+ ;; out exceeding max-specpdl-size.
+
(let ((return t))
(with-syntax-table sgml-tag-syntax-table
(while (>= arg 1)
[-- Attachment #3: Type: text/plain, Size: 1076 bytes --]
In GNU Emacs 23.1.1 (i486-pc-linux-gnu, GTK+ Version 2.16.5)
of 2009-08-03 on raven, modified by Debian
configured using `configure '--build=i486-linux-gnu' '--host=i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs23:/etc/emacs:/usr/local/share/emacs/23.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.1/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/23.1/leim' '--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -g -O2' 'LDFLAGS=-g' 'CPPFLAGS=''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_AU
value of $XMODIFIERS: nil
locale-coding-system: iso-latin-1-unix
default-enable-multibyte-characters: t
next reply other threads:[~2009-09-21 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 22:48 Kevin Ryde [this message]
2009-09-22 21:45 ` bug#4512: 23.1; html-mode C-c C-f on runs of <P> Stefan Monnier
2016-01-21 20:37 ` Alan Third
2019-06-27 1:54 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skefhq37.fsf@blah.blah \
--to=user42@zip.com.au \
--cc=4512@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).