Dotfiles VS nvim-treesitter-textobjects

Makefile -> https://github.com/beauwilliams/Dotfiles/commit/c10dad3ea6c126ac8be5afd29d1bd942b07fc16d

See the commit I made to support the new update here

I've attempted to document my dotfiles as I go. So hopefully this comes in use for you!

AFAIK I just pasted the entire config right into a file in my /plugin directory. Works great. https://github.com/beauwilliams/Dotfiles/blob/master/Vim/nvim/plugin/wilder.vim

If you want some dotfiles that are well documented, check these out

This auto-resizing function was a piece of vimscript originally, you can find that in my init.vim line 434

See my vimrc for an example of a well documented rc. This one is designed so that other people can quickly pick up from my own configs :) Vim Config

Thank you! It looks like nvim-treesitter-textobjects is a good plugin to start with:

https://github.com/nvim-treesitter/nvim-treesitter-textobjec...

Thanks! I just started using https://github.com/nvim-treesitter/nvim-treesitter-textobjects, and it works as a charm.

nvim-treesitter-textobjects

Or even better, one can use nvim-treesitter-textobjects. It already provides function/class selection and go-to functionality out-of-the-box.

You could look into treesitter-textobjects and treesitter-textsubjects: they define "smarter" blocks and function boundaries that work relatively well with python and non-parentheses code.

These are the problem. I have no issue with vanilla vim inside/around motions with nnoremap mi vi, but I can't use all extra inside/around motion plugins like mini.ai and nvim-treesitter-textobjects.

Your config, tree-surfer or nvim-treesitter-textobjects follow nodes using the syntax tree. Go to parent / child / next siblings ect....

I recently wrote a few tests here and it works with github actions as well.

There is nvim-treesitter/nvim-treesitter-textobjects. It serves double purpose: defines per-language queries for which tree-sitter nodes should be considered a function, class, etc. and defines textobjects.