nXML highlighting problem

nXML highlighting problem

[Allin Cottrell]

I'm using GNU Emacs 26.3 and current nxml on Arch Linux. A fairly
recent update (sorry, can't date it exactly) has brought a change in
highlighting behavior which I'd very much like to revert.

Namely, it seems that a plain apostrophe in XML text is now being
treated as a delimiter that calls for a change of face. So after the
first (single, possessive) apostrophe in the text the rest of the
document is shown in "within delimiters" mode.

I'd be grateful if anyone can tell me how to stop this from happening.
I've done C-h M but I couldn't find an answer there.

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC

Re: nXML highlighting problem

[Stefan Monnier]

> I'm using GNU Emacs 26.3 and current nxml on Arch Linux. A fairly
> recent update (sorry, can't date it exactly) has brought a change in
> highlighting behavior which I'd very much like to revert.
>
> Namely, it seems that a plain apostrophe in XML text is now being
> treated as a delimiter that calls for a change of face. So after the
> first (single, possessive) apostrophe in the text the rest of the
> document is shown in "within delimiters" mode.

That would be a bug, so please report it as such.


        Stefan

Re: nXML highlighting problem

[Allin Cottrell]

Ah, when I went to construct a minimal test case I realized things are
not quite as I stated in
https://lists.gnu.org/archive/html/help-gnu-emacs/2019-09/msg00157.html

The XML text is shown in "within delimiters" mode not after the very
first apostrophe but after the first apostrophe following an error in
my XML, namely forgetting to escape the "greater than" sign in an
embedded TeX fragment, $k>0$.

Somehow emacs 26.2 took that error in stride, while it chokes emacs
26.3. But not a bug, I guess. The only reason it took me a while to
spot my error is that the signs of malaise from emacs 26.3 didn't
appear until the next apostrophe came along.

Anyway, in case it's of any interest here's a minimal example:

<?xml version="1.0"?>

<p>Here's some TeX: $k>0$ (oops!). And here's what the text that
comes afterward looks like.</p>

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC

nXML highlighting problem

[Yuri Khan]

On Thu, Sep 26, 2019, 01:32 Allin Cottrell <cottrell@wfu.edu> wrote:

> The XML text is shown in "within delimiters" mode not after the very
> first apostrophe but after the first apostrophe following an error in
> my XML, namely forgetting to escape the "greater than" sign in an
> embedded TeX fragment, $k>0$.
>
> Somehow emacs 26.2 took that error in stride, while it chokes emacs
> 26.3. But not a bug, I guess.

Unescaped greater-than is well-formed in XML. The only case where it MUST
be escaped is when representing a ]]> sequence inside a <!…[…[…]]>.

> <?xml version="1.0"?>
>
> <p>Here's some TeX: $k>0$ (oops!). And here's what the text that
> comes afterward looks like.</p>

Re: nXML highlighting problem

[Allin Cottrell]

On Thu, 26 Sep 2019, Yuri Khan wrote:

> On Thu, Sep 26, 2019, 01:32 Allin Cottrell <cottrell@wfu.edu> wrote:
>
>> The XML text is shown in "within delimiters" mode not after the very
>> first apostrophe but after the first apostrophe following an error in
>> my XML, namely forgetting to escape the "greater than" sign in an
>> embedded TeX fragment, $k>0$.
>>
>> Somehow emacs 26.2 took that error in stride, while it chokes emacs
>> 26.3. But not a bug, I guess.
>
> Unescaped greater-than is well-formed in XML. The only case where it MUST
> be escaped is when representing a ]]> sequence inside a <!…[…[…]]>.

OK, so the behavior I'm seeing does seem to be a bug in 26.3. I'll
submit a report.

--
Allin Cottrell
Department of Economics
Wake Forest University