vim-textobj-user VS vim-gitgutter

Using lazy, it throws the error 70% of the time. when it doesn't throw the error it works. but It uses a dependency (vim-textobj-user) and I already tested it (only using that plugin without other plugins) is not the dependency's fault.

Just to add to that, there are also various plugins that give you additional text objects, such as: - ii for indent levels (https://github.com/kana/vim-textobj-indent) - iz for folds (https://github.com/kana/vim-textobj-fold) - if for functions (https://github.com/kana/vim-textobj-function) - ic for comments (https://github.com/glts/vim-textobj-comment) - User-defined text objects (https://github.com/kana/vim-textobj-user)

Thank you, kind vimmer. For others stumbling upon this issue, having same character around is not supported in textobj-user, but there's a workaround: https://github.com/kana/vim-textobj-user/issues/48.

The vim-wordmotion plugin extends the idea of words to include snake case and camel case words among other things. On a related note, the vim-textobj-user plugin lets you extend vim's understanding of text objects.

if anyone wants to use this, just make sure to also install https://github.com/kana/vim-textobj-user for it to work

I would highly recommend https://github.com/kana/vim-textobj-user. Specifically, you'd want to pair it with https://github.com/sgur/vim-textobj-parameter. Check the readme for other useful custom text objects, personally I think this is one of my most useful set of plugins

I NEVER use count, because my mental flow is drastically hindered by pausing for any form of counting in midst of editing; I stay off even relative numbers even. In their place, I enable a vast number of text objects instead, quite a few implemented through the `kana/textobj-user plugin`. Good text object are an embodiment of intent and thus map better mentally than any method using brute counting, even at the loss of some precision and speed.

[kana/textobj-user](https://github.com/kana/vim-textobj-user)

I would suggest using vim-textobj-user. Someone has already implemented a path object using this plugin. You can find this implementation here.

I personally use nerdtree. Add nerdtree-git-plugin too, that's nice when looking at your project (for files, use vim-gitgutter).

vim-gitgutter

That said, Neovim can still run most Vimscript plugins just fine, so you can still use https://github.com/chrisbra/changesPlugin (and https://github.com/airblade/vim-gitgutter and https://github.com/mhinz/vim-signify/, which are mentioned in the README) if you want.

vim-signify or git gutter can do this for files managed by git.

https://github.com/tpope/vim-fugitive https://github.com/airblade/vim-gitgutter Since your already on neovim these plugins are excellent for git integration within vim! You may just prefer lazygit but having a tight integration in editor is definitely really nice for my personal workflow. Your approach is more unix-y where you have a tool for each job though!

Git gutter Git status signs in the gutter (leftmost column)

vim-gitgutter supports staging/undoing hunks and a hunk text object. I find it convenient for this exact workflow.