Kiyoon Kim
Kiyoon Kim
Maybe some people use custom captures or captures from other plugins. Should we deprecate the use of `make-range!` but remove the code a little later so it won't break any?
Since we are going to keep the queries in sync with the master, the main branch will likely have `#make-range!` directives for some time. And merging this will break this...
From what I understand we would target that on master and rebase it on main when nvim-0.10.1 is out.
I also don't mind freezing `master` and focusing on updating `main` which won't break much for the existing users and even encourage them to migrate.
The development is now done in `main` and `master` is frozen. Can you open a new PR with this feature?
So the query names in `nvim-treesitter` seem to have been changed. I guess we need to update the README.
Can you install nvim and try again?
Can you run the script directly with tmux with the same arguments? I think it will at least say where it went wrong
I think you forgot the last argument '%7' which is a tmux pane identifier. What happens with that?
Can you run this command? ```bash nvim -u ~/.tmux/plugins/treemux/configs/treemux_init.lua ``` The "lazy.nvim" is a package manager, and it should be automatically installed but in your case it doesn't do that....