-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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:
|
Syntax highlighting for typescript using Tree-Sitter can be enabled with:
There are still bugs, and many themes will not work right. Next steps:
|
I don't believe this is correct
I was having problems in my implementation when having many edits across many lines all at once |
As a fellow Tree-sitter implementer, I'm duty-bound to point out the Tree-sitter implementation I did for Pulsar (a fork of Atom). Maybe it'll be useful as a second opinion when it's not clear how Zed is doing things. I had Atom's original Tree-sitter implementation from 2017ish to refer to when writing mine, so it's only fair. |
* Colorization tests for tree sitter Part of #210475 * Fix tests * Actually fix tests * Fix line endings
* Colorization tests for tree sitter Part of #210475 * Fix tests * Actually fix tests * Fix line endings * Register preferTreeSitter setting
Updates (though I didn't get to work on this October):
For November, the main plan is performance. |
* Add an easy way to run performance tests for tree-sitter Part os #210475 * Compile build folder
Goals of the explorations:
The text was updated successfully, but these errors were encountered: