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
{{ message }}
This repository has been archived by the owner on Apr 1, 2020. It is now read-only.
The Pug language has two types of comments: buffered and unbuffered.
A buffered comment is one that will get parsed to the output HTML as
<!-- -->
:// I am a comment that will be parsed to output body h1 This is a title p This is a paragraph
An unbuffered comment is one that will not get parsed to the output HTML as
<!-- -->
://- I am a comment that will *not* be parsed to output body h1 This is a title p This is a paragraph
The default "comment" key binding in Sublime Text is for an unbuffered comment
If I override that, and/or manually change every comment to be the buffered type
I'm thinking that One Dark should somehow recognize that those buffered comments should be highlighted like the unbuffered ones.
I peeked at
One Dark.tmTheme
(not sure if this applies to Sublime Text or not), and found this bit of code:Maybe this could be modified somehow to recognize Pug's
string.comment.buffered.block.pug
, shown here:¯\_(ツ)_/¯
The text was updated successfully, but these errors were encountered: