A Vim distribution with sane, modern defaults, a custom theme, and a collection of tightly integrated and configured development-oriented plugins
Find a file
2014-04-01 23:21:03 -04:00
vim Wrapped lines now display. 2014-04-01 23:21:03 -04:00
.gitmodules Added a new script that can be used to update the repo if bash is 2014-04-01 00:03:52 -04:00
README.md Updated the README to reflect the change in update script 2014-04-01 01:34:57 -04:00
update Added a new script that can be used to update the repo if bash is 2014-04-01 00:03:52 -04:00
vimrc Set the guifont to Droid\ Sans\ Mono\ 12 for those with the fontconfig hook, and if that's not what's used, set it to the font you need :) 2014-02-23 22:32:56 -05:00

Darkcloud Vim Theme, Config and Plugin Selection

Requirements

  1. Git: Required to clone and update the repository.
  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. Bash (optional): Required to use the update script, which simply runs the git repo and submodule update commands.
  5. Powerline Fonts (optional): Required for the powerline lightline theme, which can be toggled in /etc/vimrc along with the gvim font

Installation

  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 'update' script in the base directory of the repo as an easy way to pull changes and update the plugins all at once.
  5. You can find a list of keybindings that were added by this config as well as a few of the ones added by plugins in 'vim/config/keyboard.vim'

Features

  • An original theme designed to be readable and aesthetically pleasing.
  • A complete default configuration to start with and work from that aims to improve compatibility and provide sane, modern standards.
  • Keyboard/mouse bindings that attempt to maintain vim's default behaviour while adding behaviour common to other text editors, improving accessibility to useful features, and making the mouse more capable (check the comments at the top of vim/config/keyboard.vim for a list of bindings and what they do).
  • A core set of plugins that add some handy features and better support for some formats (you may want to remove plugins in vim/bundle/ supporting formats you won't be using).

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.