Use a package setting to override the block comment directive syntax about ecmascript-sublime

[bathos]

It seems reasonable to me to make the syntax: prefix optional. If that aligns with how others are doing this, it’s definitely a lot simpler than adding a runtime thingie for generating (and then managing?) custom definitions.

[bathos]

AFAIK, doing this would require generating new versions of the syntax definition dynamically in response to settings changes, implying a runtime component to this plugin that doesn’t currently exist. My guess is that it would be possible. Maybe there’s some prior art out there for this?

@blake-regalia is that correct, or do you know of other mechanisms by which user variables could be used in sublime syntax definitions?

[blake-regalia]

Not feasible. Syntax definitions currently have to be static in Sublime Text other than the way @bathos describes.

@joshfester i'd be curious to know how do the other editors/plugins use such directives? Keep in mind that we also support highlighting triggered by a few template tags such as html and css (which we should probably document).

[joshfester]

@blake-regalia it seems like most of them use /* {SYNTAX_NAME} */. However, I believe template tags would also be a great solution. I was not aware there was support for that!

[joshfester]

That would be perfect!

[blake-regalia]

@joshfester see 2.4.0.

I'm going to close this issue for now but I am still interested in dynamic or user-generated nested syntax capabilities. Feel free to open a new issue for that if you'd like.