5 ms·
In the well over 20 years I've used vim, I've always just installed and used whatever plugins I liked. Occasionally there were conflicts or problems caused by
by pmoriarty 10y ago
In the well over 20 years I've used vim, I've always just installed and used whatever plugins I liked.
Occasionally there were conflicts or problems caused by plugins, and then I just troubleshot those and uninstalled or disabled plugins until I found the culprit. No big deal.
Whenever I use another computer that just has vanilla vim installed, without my own .vimrc on hand, I just touch ~/.vimrc and away I go. I just try not to spend too much time on such systems before loading up my own .vimrc. Again, not a big deal.
I really don't get people who deliberately cripple themselves by using fewer plugins or features than were maximally useful.
On the other hand, I was never a big fan of giant plugins that make a lot of choices for you. I like to make my own choices as much as possible, and know why and how these choices are made. So the plugins I install tend to be very specific plugins that are good at one particular thing that I feel vanilla vim is lacking.
- exDM69 10y agoI like the fact that my vimrc is easy to deploy on new machines without having to hassle with plugins. At one point in the past, I did have a bunch of plugins (nerdtree, fugitive, surround, nerdcommenter, etc, etc) but they weren't that great (I guess because vim's scripting facilities and UI isn't optimal for writing complex IDE-like features) and were always conflicting or otherwise a hassle. These days I get by with vanilla vim with a conservative vimrc and I don't consider my productivity crippled. The only plugins I miss are surround.vim and a commenting plugin. If you like to try any plugins, sure go ahead but I don't think it's a good idea for someone new to vim.
- astrobe_ 10y agoWhat do you use instead of fugitive?
- exDM69 10y agogit on the commandline together with tig.
- majewsky 10y agoWhile I read this thread, I actually noticed that I use only a single feature out of vim-fugitive, which is the :Gw command. So I replaced vim-fugitive by https://github.com/majewsky/devenv/blob/master/vim/plugin/minimal-git-support.vim https://github.com/majewsky/devenv/blob/master/vim/plugin/mi... just now.
- pmoriarty 10y agoFor someone new to vim, I agree. They should really get used to vanilla vim before moving on to using fancy plugins. But once you have a good grasp of vanilla vim, I don't think there's any good reason to avoid plugins. When I install my own .vimrc on another computer, I just copy my whole ~/.vim directory over with it, and that's really all it takes to migrate. Easy. As for plugin conflicts, I've found them to be pretty rare, and when they happen they've been easy enough to troubleshoot and then I just disable the incompatible plugin, if I can't find some other fix. The occasional incompatible plugin is no reason to avoid plugins as a whole.
- majewsky 10y ago> The only plugins I miss are surround.vim and a commenting plugin. Incidentally, surround.vim and commentary.vim are also why I wouldn't want to live without plugins. Everything else is expendable.
- opium_tea 10y agoAny idea why a surround feature isn't in vanilla Vim? It seems to follow the Vim philosophy, i.e. enacted with a command that has action and movement components.