A theme, config and collection of plugins for Neovim
Find a file
Kevin d1a1622889 Removed shift-a because that's the key combo for 'A' (insert at end of
line)- whoops! Instead \a has been added, and select all has been added
to visual mode in both forms.
2014-03-28 11:44:12 -04:00
vim Removed shift-a because that's the key combo for 'A' (insert at end of 2014-03-28 11:44:12 -04:00
.gitmodules Added a writeup of features and some information about accessing them to 2014-03-28 11:13:10 -04:00
README.md Added a writeup of features and some information about accessing them to 2014-03-28 11:13:10 -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 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

  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).

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.