-
Notifications
You must be signed in to change notification settings - Fork 129
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
Add matlab grammar #185
Add matlab grammar #185
Conversation
89037f9
to
8f084e8
Compare
Ok, a lot of force-pushes later, I have what is considered the final version of the parser itself. I would like to know if there are changes that need to be made to the query file, as I'm currently using it and it works just fine, but I'm not familiar with the way your project handles those. I believed I have followed the instructions correctly, but I could not find a complete list of available query captures, so I don't if I missed something. This parser was just accepted in Neovim (nvim-treesitter/nvim-treesitter#4944), and I mention that to show that, even though it is new, it went through a revision and got some changes and bug fixes already, and I consider it to be in a stable/release version. It will see bugfixes in the future, but not major changes. |
2c53c6c
to
a2ada53
Compare
I got the queries from the elisp file, so now it should be 100% compliant. |
eea9ab7
to
a2a7476
Compare
Changes look good to me. Just wondering if we should do something about |
I set it to an empty list and it worked for me, but I must admit that I have no idea what that should actually be. |
7f3a3f1
to
8bb494f
Compare
In the last 2 force-pushes I bump the repo version because I fixed some bugs in the parser and also change the priority of the operators captures in highlight so single-quoted strings get highlighted correctly. |
This is more of a |
No description provided.