A theme, config and collection of plugins for Neovim
Find a file
2014-02-22 03:34:59 -05:00
vim Fixed some wording in the theme template 2014-02-22 03:34:59 -05:00
.gitmodules Readded bundles as git submodules 2014-02-21 00:26:50 -05:00
README.md Fixed a few small errors in the README 2014-02-21 01:00:08 -05:00
vimrc Initial commit with a relatively well configured package (config, theme and plugins), and a README to explain the details 2014-02-20 23:24:20 -05:00

Darkcloud Vim Theme, Config and Plugin Selection

Requirements

  1. Git and Bash: Required to manage plugin updates using the "pathogen_update_plugins" script.
  2. CTags: Available @ http://ctags.sourceforge.net, this can be in $PATH or in the vim folder and is required for the tagbar plugin.
  3. Vim v7.4+: Everything has been written and tested using Vim 7.4.135, and I assume there could be issues with 7.3 and below.
  4. Powerline Fonts (optional): Required for the powerline lightline theme, which can be toggled in /etc/vimrc along with the gVim font

Installation/Setup

  1. Clone this repository then initialize and update the git submodules (in our case, the vim plugins)
  1. Edit the 'vimrc' file and select whether to expect powerline fonts, choose a font for gVim, and add or change any of the loaded config files to match your personal setup.
  2. There are two main ways this package can be deployed: system-wide or single-user.
  • For a distro-agnostic system-wide installation in the /etc directory, copy or link: 'vimrc' to '/etc/vimrc' -and- the 'vim' folder to '/etc/vim'.
  • For a single-user installation in a user's home directory, copy or link: 'vimrc' to '/.vimrc' -and- the 'vim' folder to '/.vim'.
  1. Make sure the 'vimrc' file and 'vim' folder are at least readable to any users that will be using the config.
  2. Clone additional vim plugin repos in the 'bundle' folder to have them loaded at startup.
  3. You can add or replace config files in your 'vimrc' file to customize behaviour.
  4. Run the pathogen_update_plugins script to update your plugins by pulling the latest changes from each plugin repo.
  5. The 'vim/config/keyboard.vim' file has a list of the commands it configures, as well as some basic examples of some provided directly by plugins (though check the plugin folder's README for a full explanation).

Credits

License

All projects cloned in the vim/bundle folder are separate and have their own licenses. Everything else is released under the MIT license.