-
Notifications
You must be signed in to change notification settings - Fork 141
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
Support tmLanguage files natively #418
Comments
My personal opinion is that native support for I do not find the idea of native This is not the first time support for
It would at least certainly have helped |
Yes, would be really nice, especially for |
Just an advisory for anyone thinking about this: Sublime does not support all tmLanguage tokens (I want to say |
Pretty sure ST has no problem with |
Just wondering ... is this just a request or is there active development on this? Seems like a really powerful upgrade and am I right that support for Typescript is dependant on this? |
@michaelblyons indeed, as well as atom, and I think ace editor (that github uses). Github uses our grammars somehow. I would love to use this crate and dify or Pixelmatch to build a snapshot regression testing suite for our vscode-ified texmate grammars, but we make heavy use of if anyone else would like to have advanced textmate features like |
I would like to make a feature request for support for tmLanguage files and/or the VSCode flavour of this. It is a very prevalent grammar format which would allow us to tap into a vastly bigger ecosystem directly. I'm aware that there are converters between the formats, however I've found that they don't work correctly in all cases. Moreover, it would save maintainers of grammars a lot of hassle to not have to maintain duplicate grammars formats for every single language.
The text was updated successfully, but these errors were encountered: