all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rolf Ade <rolf@pointsman.de>
To: Allin Cottrell <cottrell@wfu.edu>
Cc: 37521@debbugs.gnu.org
Subject: bug#37521: breakage in emacs 26.3 + nxml
Date: Fri, 27 Sep 2019 02:03:27 +0200	[thread overview]
Message-ID: <87h84ymwq8.fsf@pointsman.de> (raw)
In-Reply-To: <alpine.LNX.2.21.1909260823070.200502@robroy> (Allin Cottrell's message of "Thu, 26 Sep 2019 08:38:20 -0400 (EDT)")


Allin Cottrell <cottrell@wfu.edu> writes:
> There's a broken interaction between unescaped '>' (ASCII 62) and
> apostrophe (ASCII 39) when editing an XML file in nxml mode in emacs
> 26.3. (Version 26.2 was OK.)
>
> At the first apostrophe following an unescaped '>', the font color
> switches to "within delimiters" mode, and, depending on the context,
> certain nxml editing commands stop working properly.
>
> Here are two little examples. The first just shows the unwanted change
> in face:
>
> <?xml version="1.0"?>
>
> <p>Here's some text, including the inequality 3 > 2. And here's
> what happens in following text once an apostrophe comes along.
> </p>
>
> The second example shows what happens when the apostrophe is inside a
> tag. If you delete the trailing "</p>" below, then try to insert it
> again via the shortcut C-c C-f, it's "</tt>" that gets inserted
> instead:
>
> <?xml version="1.0"?>
>
> <p>Here's some text, including the inequality 3 > 2. And here is an
> apostrophe inside a tag: <tt>'</tt>. Plus some following text and
> so on.</p>

Current master

commit fd6f4bf648c5a4417eb591a8c54b87c7c60de154
Author: Nikolaus Rath <Nikolaus@rath.org>
Date:   Fri Sep 27 01:39:13 2019 +0200

works like 26.2 (that is: correct).





  reply	other threads:[~2019-09-27  0:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 12:38 bug#37521: breakage in emacs 26.3 + nxml Allin Cottrell
2019-09-27  0:03 ` Rolf Ade [this message]
2019-09-27  0:26 ` Rolf Ade
2019-09-27 11:22   ` Rolf Ade
2019-10-02 23:40     ` Noam Postavsky

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=87h84ymwq8.fsf@pointsman.de \
    --to=rolf@pointsman.de \
    --cc=37521@debbugs.gnu.org \
    --cc=cottrell@wfu.edu \
    /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.