Broken highlighting in Build 3154

[n-kort]

Also posted over at sublimehq/Packages#1302

[Thom1729]

The way that I would fix this is by using the new embed feature, like the core HTML syntax does. This would require updating the syntax definition to the sublime-syntax format, which would break compatibility with ST2. I'm not familiar enough with the tmLanguage format to say whether there is a solution within that system.

[yyx990803]

I'd love to rewrite this using the sublime-syntax format, but currently don't have time to do so myself. If anyone wants to take a stab at it that would be awesome..

[skyronic]

There's a temporary workaround to fix this with the current tmLanguage file: Install the Babel extension and use package manager to disable the JavaScript package (important to disable JS package). This seems to fix it for me. Can you try this @n-kort

[n-kort]

@skyronic doesn't quite work for me:

Just loses all highlighting in the <script/> block. This was after installing the Babel package and adding "JavaScript" to "ignored_packages"...

[skyronic]

@n-kort can you have your cursor somewhere in the script block and press control+shift+p (OSX) or ctrl+alt+shift+p (Windows and Linux).

It should pop up some text. can you paste that here?

[n-kort]

text.html.vue
source.js.embedded.html

with the cursor just after 'bar'

[skyronic]

Ok. I'll send a early version of the syntax definition sometime within 12 hours, hopefully you can try that and tell me if it works for you :)

[skyronic]

@n-kort can you try the instructions from the PR at #109 and tell me if that fixes your issue?

[skyronic]

@n-kort @yyx990803 I can confirm that in the latest dev build of sublime, it seems to be working when I disable JavaScript and install Babel. In fact, I'm thinking the issue is actually with sublime's JS implementation.

Please see https://gfycat.com/anotherseriousfritillarybutterfly for a quick screencast.

[skyronic]

Filed an issue with Sublime for their JS syntax implementation which looks wrong sublimehq/Packages#1309

@Thom1729 if possible, can you verify if my issue is valid and is something that needs to be fixed from Sublime's end?