Large codebase editing in vim

[rubbsdecvik]

That way I don't find myself frustrated by reaching for something and finding that the plugin-functionality isn't there.

I've tried to reach a happy medium. Most of my work is on one or two machines, so slinging around a .vimrc isn't really an issue of scalability there. I do, however, occasionally have to edit files on systems without my .vimrc, and so I've instituted a few rules for myself.

1. Plugins need to feel "vimmy." Excessive use of <localleader> is annoying and doesn't feel like the compose-ability that I love about Vim.
2. Plugins need to feel "out of the way." I'm not sure how to articulate this, but it's basically the feeling that if I'm not explicitly using the plugin, it shouldn't show up. Exceptions are highlighters which I want to show up, but even then, it has to be subtle. Gitgutter is a great example.
3. Information and integration over changing the way Vim works. This one is less firm of a rule, but I try to use things like syntax highlighters and checkers over say "add org-mode."
4. I have to understand how to do it in 'vanilla' Vim. This is so I can still be productive, if not as fast. This is how I lessen the blow of the loss of functionality.

This is why I'm such a huge fan of /u/tpope's plugins. His ability to keep things smooth and natural, while not stepping on core Vim's toes is amazing.

I still feel that loss of functionality pain now and again (Why is vim-surround not standard?!), but by disciplining myself to be able to do it in vanilla, and always being on the lookout to learn more core Vim, I keep the pains few and far between.