focus.nvim VS vim-textobj-user

focus.nvim

For automatic and probably instant split resizing, you could use focus.nvim or something similar. Or just resize using Neovim (keyboard) commands, which probably would also not lag.

- https://github.com/beauwilliams/focus.nvim

Been searching around, and found zen-mode and focus.nvim but they don't really fix my specific use case. Some even suggested to have the file explorer opened to act as the left padding.

I mean... yeah? I write vim plugins, see focus.nvim

For those that haven't heard of focus, a quick TLDR.. if you love using vim splits, you will find focus.nvim makes your life with splits just that little bit better. The core feature of focus is auto-resizing splits, when moving between them the currently focused window will be resized to take up more of the screen. It's even more awesome now thanks to #1 below. Or maybe see some demo gifs here.

Hmm, perhaps this can be an addition to focus.nvim ..maybe add some options and enhancements to make it work better

You can also get auto-resizing splits like in this little thing I wrote focus.nvim

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.