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
One can notice that /* is classified as a comment and is continued for the rest of the document. A temporary fix is creating a comment in the next like using // or # and ending the multiline comment by using */
{
key: "value /*"
// */
}
The reason this exists is because the syntax-propertize-function is of higher priority than font-lock-defaults and I can't work out how to disable comments in the syntax-propertize-function which are placed where strings are parsed.
The text was updated successfully, but these errors were encountered:
This is way outside of my wheelhouse, but I wrote the current version of the Hjson syntax highlighting for TextMate-like editors (Atom, VS Code, etc.). To solve this problem, I had the regex for a quoteless string value consume text through the end of the line (see here). Maybe you could add something in your hjson-highlights section that highlights such strings?
Steps to reproduce:
One can notice that
/*
is classified as a comment and is continued for the rest of the document. A temporary fix is creating a comment in the next like using//
or#
and ending the multiline comment by using*/
The reason this exists is because the
syntax-propertize-function
is of higher priority thanfont-lock-defaults
and I can't work out how to disable comments in thesyntax-propertize-function
which are placed where strings are parsed.The text was updated successfully, but these errors were encountered: