darkcloud-nvimconfig/README.md
Kevin 46be09900c Added a new script that can be used to update the repo if bash is
available. Updated the README. Improved the theme by adding a bunch
of syntax highlighting definitions (mostly rooted in html, though
a bunch of other languages base their colours on it), as well as
tweaking visual selection to longer invert on the block with the cursor,
and parenthesis matching to look the same at both ends. Added a plugin
that improves the theme and adds some keyboard shortcuts to markdown,
which is what the README.md files in Github are written in. I realized
that the h,j,k,l shortcuts equivalent to the ones with arrow keys I'd
added were overwriting other shortcuts with the shift combinations, so
I removed those and the ctrl-ones for consistency. The diff shortcuts
weren't intuitive or easy on the hands, so I tried something else and
I think it works much better now (check vim/keyboard.vim). An update
script has also been added to simplify updating submodules; I'm not
completely clear as to whether following this method will properly
update the submodules in certain conditions like when one is removed,
but this should add new ones and update the existing ones after pulling
from the repo.
2014-04-01 00:03:52 -04:00

3.3 KiB

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