vim-blueplanet VS vim-textobj-user

To my knowledge vim-test has no out-of-the-box configuration for TypeScript. I forgot why. Anyway here is my configuration that adds mocha and jest as testers for TypeScript. Though it is mostly based on the existing JavaScript support of vim-test it adds some extra support for Vue testing and project local binaries. Finally ensure you enabled these testers in the vim-test configuration (g:test#custom_runners).

You could take a look here at my configuration. Not sure if that is helpful. You should first read up native packages as it has been linked above. I don't explain the little sneaks and features here. But in its core I put file and directory structure above everything else. I barely import anything manually but fully rely on automated mechanisms. I use lazy loading heavily. I use a mix of .vim and .lua files depending on its content and which language is easier (e.g. mappings are simpler in VimL. In result I have hundreds of files in my configuration. My everything follows a structure. With tools like fzf or telescope it is too easy to open the file you search for. It's basically no overhead. It would be more work to find what I search for if I would have less files. Finally this keeps everything incredibly independent. I can add, change and especially remove thing very easily as most things are very separated and independent. I want to remove a plugin, all its config, mappings, highlights, signs, ... I just remove one directory. Nothing more and nothing less. Clean cut. If I want a plugin and everything around it (copy-paste from above) to be lazy loaded it just works out-of-the-box. It's very simple and elegant. In my opinion. Though you can easily dislike it if you don't agree that strong with the approach it's fundamental arguments.

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.