From: npostavs@gmail.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: Moritz Bunkus <moritz@bunkus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
32823@debbugs.gnu.org
Subject: bug#32823: 26.1; nxml-mode: "no matching start-tag" with long entity definition list
Date: Mon, 27 May 2019 15:22:45 -0400 [thread overview]
Message-ID: <85muj7d7ne.fsf@gmail.com> (raw)
In-Reply-To: <838t3q9ibf.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 25 Sep 2018 09:56:04 +0300")
merge 18871 32823
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> Maybe you're doing something slightly different than I am. I've created a
>> short screencast showing both nxml-finish-element not working and working
>> after the entity definitions have been removed:
>>
>> https://www.bunkus.org/misc/nxml-mode-bug-32823-01.webm
>>
>> Maybe that'll help.
>
> It did, thanks. Turns out I was trying "C-c C-f" on the wrong
> refentry line (there are too many of them).
>
> Anyway, it sounds like the problem is with using syntax-ppss: its 8th
> element is nil in the "good" invocation and non-nil in the "bad" one.
I believe this bug is a dup of #18871, the root of the problem is that
the bounds of the prolog (DTD definition) aren't updated after editing.
Should be fixed by the patch in https://debbugs.gnu.org/18871#30
next prev parent reply other threads:[~2019-05-27 19:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 12:50 bug#32823: 26.1; nxml-mode: "no matching start-tag" with long entity definition list Moritz, Bunkus <moritz
2018-09-24 16:25 ` Eli Zaretskii
2018-09-24 17:12 ` Moritz Bunkus
2018-09-24 17:26 ` Eli Zaretskii
2018-09-24 17:51 ` Moritz Bunkus
2018-09-25 6:56 ` Eli Zaretskii
2019-05-27 19:22 ` npostavs [this message]
2019-05-27 20:01 ` Moritz Bunkus
2019-05-27 20:35 ` npostavs
2019-05-28 15:39 ` Moritz Bunkus
2019-05-29 23:40 ` Noam Postavsky
2019-05-30 13:22 ` Moritz Bunkus
2019-05-30 22:08 ` Vincent Lefevre
2019-06-02 17:50 ` Vincent Lefevre
2019-06-04 12:59 ` Noam Postavsky
2019-06-04 14:29 ` Vincent Lefevre
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=85muj7d7ne.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=32823@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=moritz@bunkus.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.