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 }}
Repository navigation
QML syntax highlighting doesn't work with build 3103 #14
I've been using your QML package with previous sublime text 3 build (3083) for quite long time now.
With a new official build (3103) syntax highlighting stops working.
I think it might got something to do with changes to syntax definition file format in new build.
I can try to fix it myself, just need some hints on where to look.
Hi all.
As I pointed in the SublimeText/QML#6 there is a regression in new ST release.
I'm waiting new release where they will fix it (I hope).
Another option is to rewrite highlighting in new language and support both implementations.
I just have no time right now to reimplement stuff.
Fast workaround is switch to prev release if QML is critical to you.
Activity
DamnWidget commentedon Feb 19, 2016
That QML package is not mine, but the author made some PR to this project as his highlighting was better then the one that I used to have in here.
Can you uninstall QML package, install SublimePySide (the package is called PySide in ST3 palette) and let me know if you encounter any issues?
rsht commentedon Feb 19, 2016
Same thing with PySide package installed (while QML package is uninstalled).
With 3013 build QML files looks like this (with PySide
xorQML)rsht commentedon Mar 11, 2016
I think that this can be closed or somehow linked to this issue at QML package repo.
DamnWidget commentedon Mar 11, 2016
Hi @shtemberko, SublimePySIde highlight support is a contribution from @skozlovf so I will close as soon as he considers it can be closed.
Thank you.
skozlovf commentedon Mar 11, 2016
Hi all.
As I pointed in the SublimeText/QML#6 there is a regression in new ST release.
I'm waiting new release where they will fix it (I hope).
Another option is to rewrite highlighting in new language and support both implementations.
I just have no time right now to reimplement stuff.
Fast workaround is switch to prev release if QML is critical to you.