vim-ReplaceWithRegister VS vim-textobj-user

With https://github.com/inkarkat/vim-ReplaceWithRegister, yiqgllA,

If you're into hidden gems: * This fixes repeat behaviour for all visual modes, like proper . in visual block. * This this provides a proper paste-over operator, working with all register types (text?,line,block).

My favourite solution to this is the ReplaceWithRegister plugin.

I would recommend this plugin to solve this kind of problems https://github.com/inkarkat/vim-ReplaceWithRegister

Thanks a lot for this recommendation! This particular repo hasn't been updated since 2014, here is a more up-to-date version by the same author: https://github.com/inkarkat/vim-ReplaceWithRegister.

The best solution I've found to this is a plug-in called Replace with register, which maps to gr (mnemonic "go replace"). This lets you just do diw, move, griw.

If you don't mind using plugins, take a look at vim-replace-with-register, which is designed to solve exactly this problem. It gives you a command, mapped to gr by default, which replaces the following text object with the contents of a register. So you can delete a word (daw), then move to a different word and replace it with the contents of the default register (graw).

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.