You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(the head-matcher may seem weird but makes sense in my project)
(note: xml-mode is an alias for nxml-mode in modern emacs)
The syntax highlighting breaks completely. It considers the whole buffer to be xml, even though mode-switching does work for other functionality.
The setup works much better with sgml-mode, although sometimes highlighting only works for the first xml block, and the following errors appear in my modeline when I edit an xml block:
(jit-lock--run-functions11721281) [span 11721281 insert-text-command-test.ts[sgml]] -> (font-lock-default-fontify-region11721281): Args out of range: 1171, 1171
(insert-text-command-test.ts is the file I'm editing on this particular occasion)
They don't seem to break anything significant though.
So in summary: default xml-mode breaks syntax highlighting (but seems to work otherwise) and the old sgml-mode works, but with some jankiness.
The text was updated successfully, but these errors were encountered:
It seems the emacs-default
nxml-mode
doesn't play nice with polymode, at least not with typescript-modeMy setup:
(the head-matcher may seem weird but makes sense in my project)
(note:
xml-mode
is an alias fornxml-mode
in modern emacs)The syntax highlighting breaks completely. It considers the whole buffer to be xml, even though mode-switching does work for other functionality.
The setup works much better with
sgml-mode
, although sometimes highlighting only works for the first xml block, and the following errors appear in my modeline when I edit an xml block:(insert-text-command-test.ts is the file I'm editing on this particular occasion)
They don't seem to break anything significant though.
So in summary: default
xml-mode
breaks syntax highlighting (but seems to work otherwise) and the oldsgml-mode
works, but with some jankiness.The text was updated successfully, but these errors were encountered: