Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QML syntax highlighting doesn't work with build 3103 #14

Open
rsht opened this issue Feb 19, 2016 · 5 comments
Open

QML syntax highlighting doesn't work with build 3103 #14

rsht opened this issue Feb 19, 2016 · 5 comments

Comments

@rsht
Copy link

rsht commented Feb 19, 2016

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.

Thanks!

@DamnWidget
Copy link
Owner

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
Copy link
Author

rsht commented Feb 19, 2016

Same thing with PySide package installed (while QML package is uninstalled).

With 3013 build QML files looks like this (with PySide xor QML)

@rsht
Copy link
Author

rsht commented Mar 11, 2016

I think that this can be closed or somehow linked to this issue at QML package repo.

@DamnWidget
Copy link
Owner

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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants