emacs 24.5 nXML regression?

emacs 24.5 nXML regression?

[Sam Halliday]

Hi all,

I just upgraded to 24.5 from 24.4 and found that emacs froze on me when I tried to uncomment (with M-:) on the final comment line of the XML below.

The only way out was to drop to the terminal and send a kill signal.

Is this a known regression in the nXML mode?

I can't use the built-in bug reporting tool, as I am behind a corporate firewall.

Best regards,
Sam

<configuration scan="true" scanPeriod="3 seconds">
  <property name="PATTERN" value="%d{dd MMM yy HH:mm:ss.SSS} %logger{0} [%X{CONTEXT_ID} %thread] %-5level - %msg%n" />
  <turboFilter class="ch.qos.logback.classic.turbo.DuplicateMessageFilter">
    <cacheSize>1048576</cacheSize>
  </turboFilter>
  <appender name="file" class="ch.qos.logback.core.FileAppender">
    <file>test-output.log</file>
    <append>false</append>
    <encoder>
      <pattern>${PATTERN}</pattern>
    </encoder>
  </appender>
  <root level="${root-level:-INFO}">
    <appender-ref ref="file" />
  </root>
  <logger name="org.apache" level="WARN" />
  <!-- <logger name="akka" level="DEBUG" /> -->
  <!-- <logger name="testing" level="DEBUG" /> -->

  <!-- <logger name="foo.bar" level="DEBUG" /> -->
</configuration>

Re: emacs 24.5 nXML regression?

[Stefan Monnier]

> I can't use the built-in bug reporting tool, as I am behind
> a corporate firewall.

M-x report-emacs-bug RET will just send an email, so if you don't want
to bother telling Emacs how to send email, you can copy&paste
the address (and ideally the body as well) into your favorite MUA.


        Stefan

Re: emacs 24.5 nXML regression?

[Sam Halliday]

On Monday, 6 July 2015 17:21:05 UTC+1, Stefan Monnier  wrote:
> > I can't use the built-in bug reporting tool, as I am behind
> > a corporate firewall.
> 
> M-x report-emacs-bug RET will just send an email, so if you don't want
> to bother telling Emacs how to send email, you can copy&paste
> the address (and ideally the body as well) into your favorite MUA.

I'm home now, and can confirm the bug on two machines. I can use report-emags-bug now.