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
Right now it's not looking so good, chiefly because of an issue with the grammar.
The only syntax file format accepted by the repository is .json, which eliminates two that you provided, leaving us with only the VS Code extension syntax. But this might be fine, since there seem to be a group of small, fixable errors with that syntax (like trailing commas accepted by some json parsers, just not the grammar parser accepted by linguist). I am trying to see if I can get a working version right now, in this fork.
So, a few things could happen from this point:
I don't get the grammar to pass the checks and either:
another jai grammar needs to be found (but, on a cursory glance, I don't see any other acceptable ones on the internet)
someone more skilled than I should try to modify the one in the VS Code repo
I do get the grammar to pass the checks in the repo. In this case, we would need the VS code extension's maintainer(s) to either
merge our changes into their repo and add a license to it
Okay, small update. I have a working syntax arrangement for the grammars now, but I just need adequate permission to use it (or a license for the syntax) from the VS Code extension repo's maintainer.
Language name
Jai
URL of example repository
https://github.com/search?q=path%3A*.jai&type=code
5.2k files
Projects using the language:
https://github.com/focus-editor/focus
https://github.com/SogoCZE/Jails
Wiki showing how the language works. Might be useful:
https://github.com/Jai-Community/Jai-Community-Library/wiki
URL of syntax highlighting grammar
https://github.com/krig/jai-mode (emacs highlighting)
https://github.com/rluba/jai.vim (vim highlighting)
https://github.com/onelivesleft/the-language (VS Code highlighting)
Most popular extensions
.jai
Detected language
none
The text was updated successfully, but these errors were encountered: