-
Notifications
You must be signed in to change notification settings - Fork 139
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
TLB syntax support for neovim #848
Comments
This etc. is rather ambiguous — do you mean a Tree-sitter parser and queries per each editor that supports it? Also, while Neovim's setup of the tree-sitter is quite simple, for Zed you have to write your own little extension in Rust :) |
For now I only meant to create a tree-sitter parser + bindings for neovim, including to add it into https://github.com/nvim-treesitter/nvim-treesitter so it's easy installable. But the tree-sitter grammar could be then re-used for editors like zed, since they also support it. |
@nickshatilo Incidentally, I've been writing Tree-sitter parser for TL-B in my free time for quite a while and will publish it this week. So we can compare implementations, if you have one already :) However, making a Neovim or Zed package would still be on the list of nice things to do, and I believe your proposal (and, if it gets accepted, your future work) may address those! UPD: Polishing the final implementation, got to squash a bug or two :) |
I have some implementation that works already, it's quite junky as of me but would be happy to refine it make it a public good! |
@nickshatilo, the bounty has been approved! Could you please reach out to me via DM for further communication? https://t.me/delovoyslava |
Summary
There is TLB syntax support in func plugin for intelleji IDEs, but not for neovim, zed etc. The goal is to add this support.
Context
Currently when using neovim, there is only syntax highlighting for func, but when editing func code it is very helpful to have proper TLB schemes in place, i.e in comments, or TLB files.
They also could be used to generate parsers for them using other tools.
This is also good for feature parity across different editors, so the ecosystem support is diverse.
References
JetBrains IDEs support
TLB parser
TLB docs
Estimate suggested reward
reward: $2000
time needed: 7-10 days
The text was updated successfully, but these errors were encountered: