-
Notifications
You must be signed in to change notification settings - Fork 172
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
Refactor into standalone plugin #503
Comments
Would a PR be welcome? |
Of course! |
Would the PR also have to remove the dependency on nvim-treesitter? |
Yes, that is the whole point! |
For reference : nvim treesitter roadmap to 1.0 now reads we'll wait nvim 0.11 before Treesitter 1.0. nvim 0.10 just got released after a very long time and now we need to wait 0.11 then (hopefully) Treesitter will be 0.10 then (hopefully) this package will be 1.0 All this could take a year or two so I find it not a great thing my PR get halt because we have to wait 1.0 #588 (comment) |
Nvim-treesitter 1.0 (expected later this year) will completely remove the module system in order to significantly reduce complexity.
This means that nvim-treesitter-textobjects needs to be refactored into a standalone plugin, similarly to https://github.com/nvim-treesitter/nvim-treesitter-context or the
indent.lua
module in 1.0. (There's no need to hook intonvim-treesitter
; textobjects should simply work if a suitable parser and queries are in runtimepath. This should also allow simplifying thesetup
as it no longer needs to be shoehorned into the nvim-treesitter setup structure.)As a bonus, the
incremental-selection
(also removed in 1.0) feature could be integrated here as ain
/an
node object.The text was updated successfully, but these errors were encountered: