From: Eli Zaretskii <eliz@gnu.org>
To: Moritz@chai-latte.bs.linet-services.de, Bunkus <moritz@bunkus.org>
Cc: 32823@debbugs.gnu.org
Subject: bug#32823: 26.1; nxml-mode: "no matching start-tag" with long entity definition list
Date: Mon, 24 Sep 2018 19:25:26 +0300 [thread overview]
Message-ID: <83zhw6ammh.fsf@gnu.org> (raw)
In-Reply-To: <cul36tzjbze.fsf@linet-services.de> (Moritz@chai-latte.bs.linet-services.de)
> From: Moritz@chai-latte.bs.linet-services.de,
> "Bunkus <moritz"@bunkus.org
> Date: Mon, 24 Sep 2018 14:50:29 +0200
>
> Note that nxml-mode always states that the document is valid
It says "invalid" here...
> 1. Save the XML code below into a file.
> 2. Start emacs -Q
> 3. Open the test file.
> 4. Place the cursor at the end of the line starting with "<refentry…".
> 5. Try using the "nxml-finish-element" function, e.g. C-c C-f. It will
> show the aforementioned error message instead of inserting "</refentry>".
> 6. Now shorten the entity definition list, e.g. by removing the whole
> line defining "ent5". Execute "normal-mode" to let nxml-mode parse the
> buffer again. Re-run the test from step 5. It will now insert
> "</refentry>" properly.
Maybe I'm not reproducing this correctly, but in my case it emits the
same error even after removing the ent5 line.
next prev parent reply other threads:[~2018-09-24 16:25 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 [this message]
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
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=83zhw6ammh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32823@debbugs.gnu.org \
--cc=Moritz@chai-latte.bs.linet-services.de \
--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.