Kiyan

That's what i thought too. It might be a bit complicated to implement match removal in a directive since as you say, these are determined during querying runtime and we...

#2471 deprecates the `used_by` property for the parser definitions. This is now set via the `filetype_to_parsername` table exported from the parsers module: ```lua local ft_to_parser = require"nvim-treesitter.parsers".filetype_to_parsername ft_to_parser.someft = "python"...

I think this might be a problem because neovims `get_parser` needs the parsers to be installed in the runtimepath i believe. @theHamsta do you think it would still be feasible...

I'll be waiting on @clason and @theHamsta suggestion about this then

I think it could also help with people using parsers installed from nix packages

@theHamsta would it be a good idea to outsource javascript extensions into a separate repo ? Things like graphql, styled components and such adds unecessary highlighting for most users, that...

I understand, although i'm pretty sure adding injection queries will slow down the querying. Doing performance regression testing would indeed be a good idea to make sure new queries don't...

I believe it's related to the syntax being disabled with treesitter, thus the matchit module cannot work as expected. I don't think there is a workaround yet @theHamsta ?

I think @alex-courtis that there is a missing thing from this. After exploring a bit i've noticed that hijacking a directory buffer indeed replaces the window on the side it...

you could give it a try if you wish :) It probably wont be done soon since i will be afk for this month.