-
Notifications
You must be signed in to change notification settings - Fork 4
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 For the Yaml version of the TmLanguage #19
Comments
definitely possible. tho it will take some time originally I had thought about doing it I can create the syntax highlighting I can get integration with RedHat's extension redhat-developer/vscode-yaml#1092 otherwise you can download this extension https://marketplace.visualstudio.com/items?itemName=pedro-w.tmlanguage or https://marketplace.visualstudio.com/items?itemName=radium-v.yaml-tmlanguage |
for backslash escaping |
Sweet! I will check out that one as well. Even just the syntax highlighting would be super helpful. Debugging the language kinda still ends up having to be in json anyway as that is what ends up getting used by vscode anyway. I do also just want to thank you for implementing the call stack thing for debugging the tokenization. It saved so much time debugging compared to having to setup the tokenization CLI and then compare back and forth. It saved my at least a few hours of tedious work. |
happy to see its in good use 🥳 slowly getting there seems the YAML repo is on the slower side atm redhat-developer/vscode-yaml#1068 |
That makes sense. I have had a few issues with the yaml extension in the past so the fact that it is strapped for resources is not surprising. Thanks again 💙 |
Would it be possible to add support for the yaml version of the textmate language definitions? From some experience it is a little nicer to write the language specs in the yaml version is that you don't have to escape the regex as much as in json. It is also mentioned on the vscode docs (https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide).
The text was updated successfully, but these errors were encountered: