-
Notifications
You must be signed in to change notification settings - Fork 31k
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
Explore using tree sitter for syntax highlighting #210475
Comments
Some notes on incremental parsing:
@hediet FYI. |
Opened tree-sitter/tree-sitter#3341 for the above issue. |
After some discussion, we've decided to first understand the performance of using tree-sitter to parse files. #213565 contains that work. |
We also need new internal editor API to write a more optimal parse function, which @rebornix may help with. |
Progress in July:
|
* Use tree sitter for ini Part of #210475 * Include ini in tree sitter colorization tests * Remove /r
* Change tree sitter setting to be per langauge Part of #210475 * Fix accidentally unregistering languages
Will using Tree Sitter make it easier to implement this (10yo) extension api feature #580 - get scopes at Position/Range? |
@usernamehw @alexr00 |
No time frame at the moment. |
* Enable bracket features with tree sitter and fix template strings Part of #210475 * Fix force tokenization
End of Febuary updates:
|
Is it possible for color themes to use scopes provided by tree-sitter? |
Currently, only scopes listed in the highligths file are available, though I'm ading more to that as we find things missing that existing themes need. Once we have a contribution story, I think we would allow extensions to contribute an scm file like that. |
If the current language lacks the tree-sitter syntax, VS Code should fall back to the current TextMate highlight syntax. |
@tats-u that is the current plan |
Goals of the explorations:
The text was updated successfully, but these errors were encountered: