-
Notifications
You must be signed in to change notification settings - Fork 26
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
Provide syntax-highlighting-files #37
Comments
Hi, failing to find a decent IDE support for zserio, I've got a chance to implement a VS Code extension myself. It provides highlighting, syntax checking, and basic symbol navigation. You can get it from https://marketplace.visualstudio.com/items?itemName=4og.zserio-language-support |
Hi @4og, Do you know if some stuff from your extension could be reused for other IDEs? Or if it would be possible to use it for "integration" with github - currently github says that *.zs is a ZenScript :-) and markdown of course doesn't know the zserio syntax as well. |
I think we should once in a while add a section of community links to the zserio README where we can reflect all these helpful tools and repos that are built around zserio and are somewhat hidden in the dark. A first shortlist could include: https://github.com/4og/zserio-language-support |
Thanks for feedback! Support for type references highlighting can be done using a semantic token provider. It fairly easy to do, so I'm going to include it in the next release. VS Code is using TextMate grammars for syntax highlighting, and they can be reused in other IDEs supporting TextMate bundles (Sublime, Atom, IntelliJ...). Linguist is also using TextMate, so it boils down to a submodule in https://github.com/github/linguist/tree/master/vendor/grammars. It might be hard to meet the popularity requirements, however. |
Would be great to have correct syntax highlighting of zs in typical editors like vim or sublime text. Maybe you could even create a pull-request for https://github.com/github/linguist later which would also enable correct highlighting in github comments.
The text was updated successfully, but these errors were encountered: