All Articles

Vim Plugins

Update 2018-10-11: plugin changes and other updates.

Overall I found that plugins makes Vim really powerful tool. However you need a lot of them and usually you should spent quite some time until you find good ones and sometimes you even have to deal with not working ones.

Another pain point might be operating system you are using and python specifics that arise from that. E.g. On Windows you have to install python 2.7, find x64 vim build and more things to get everything working properly. Therefore I’m really happy that I don’t have to deal with Windows anymore. Situation on Linux is better but still not perfect. E.g. on newest Ubuntu version Gvim is compiled with Python 3 (that’s good) but some plug-ins have not migrated to Python 3. Yes, in the end of year 2018. But enough rants! Let’s move to plug-ins I use and not use anymore. If you have questions, do not hesitate and ask.

For plugins I use vim-plug plugin manager https://github.com/junegunn/vim-plug. It is really simple and works really well. Previously I was using Vim’s native packaging system (:help packages) which works fine with all the plugins I use but it is hard to keep plug-ins up to date easily. I am storing my configuration files using this model in git https://developer.atlassian.com/blog/2016/02/best-way-to-store-dotfiles-git-bare-repo/ and tried using git submodules for plugins. It was good until you need to remove plugins from multiple machines. As well usage of git submodules adds unnecessary layer of complexity.

Here I’m trying to list plugins by category.

Generic programming plugins:

Git:

Python:

Javascript:

Status line:

Other:

Plugins, that I’m not using anymore:

As well you can checkout my .vimrc here with newest list of plugins: https://bitbucket.org/daliusd/cfg/src