After only a couple of days I did start finding git submodules annoying (again… who knew?). In order to get them out of my configs I’ve moved over from pathogen to Vundle. Pathogen lets all of your plugins behave like Mac Apps and line in their own little folders, instead of coexisting with other vim files in a single vim runtime folder (normally ~/.vim). Vundle takes this same approach but manages the git cloneing and updating of these plugins. So instead of autoloading whatever is in a folder, you define what plugins you want and are then able to install/update them from inside git.

While writing my imports plugin I learned about vim’s autoloading feature. This started as me being confused (while looking at other plugins) about why some things were in the autoload folder and some were in the plugins folder. To me both folders appeared to be autoloaded at startup… but this isn’t the case!

This project is NOT ready for full publication yet… it’s also not totally tested by me yet, but I want to write about how it works and how I learned enough vimscript to make it work.

This first post will be about everything I had to install to get Vim working in windows. If you try this out and run into any issues please let me know so I can fix things. I never know what I’ve installed years ago that ends up helping something out. It should also go without saying that in linux I use the default package manager for all of this. On a mac I use homebrew. Both are much simpler since a sane terminal is already installed.

Recently when looking up information about front end libraries (Angular, Ember, etc… will blog about this later on I’m sure) I realized that Yehuda Katz works on a vim config distribution called Janus. I’ve been having a lot of trouble moving off of IntelliJ onto Emacs at work so I figured it was worth a shot to try out Vim again.