-
-
Notifications
You must be signed in to change notification settings - Fork 279
Upstreaming 5/n - Cleanup syntax files #504
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
Conversation
Looks like it ran. |
Is this related to the sections like HEAD: {...} and headlines like |
Yea, but that's all unchanged. All this PR is doing is removing the The advantage of that is:
|
You are 100% right, and not really related at all. The next PR in the stack addresses filetypes (the linked issues), and I came to the conclusion we can have the best of both worlds: custom filetypes for neogit buffers, and treesitter parsers turned on (if available). I think its very handy to be able to define behaviour that doesn't leak out, but, like I said, thats up next :) |
Agreed, it is advantageous to make use of treesitter rather than our own hand rolled regexes |
This is just a general cleanup of the syntax files. A lot of the sign definitions have been extracted to a lua file, as well as highlight definitions. Makes it easier to do dynamic highlights/signs and prevent issues for users who have syntax disabled.