2016-01-04 18:00:36 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
2016-01-04 18:40:32 +01:00
|
|
|
#### Basics
|
|
|
|
|
- [Colorschemes?](#colorschemes)
|
|
|
|
|
|
|
|
|
|
#### Usage
|
2016-01-04 18:00:36 +01:00
|
|
|
- [Managing plugins](#managing-plugins)
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
2016-01-04 18:40:32 +01:00
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
#### Colorschemes?
|
|
|
|
|
|
|
|
|
|
Colorschemes are the way to style your Vim. Vim consists of many components and
|
|
|
|
|
each of those can be customized with different colors for the foreground,
|
|
|
|
|
background and a few other attributes like bold text etc. They can be set like
|
|
|
|
|
this:
|
|
|
|
|
```viml
|
|
|
|
|
:highlight Normal ctermbg=1 guibg=red
|
|
|
|
|
```
|
|
|
|
|
This would paint the background of the editor red. See `:h :highlight` for more
|
|
|
|
|
information.
|
|
|
|
|
|
|
|
|
|
So, colorschemes are mostly a collection of `:highlight` commands.
|
|
|
|
|
|
|
|
|
|
Actually, most colorschemes are really 2 colorschemes! The example above sets
|
|
|
|
|
colors via `ctermbg` and `guibg`. The former definition will only be used if Vim
|
|
|
|
|
was started in a terminal emulator, e.g. xterm. The latter will be used in
|
|
|
|
|
graphical environements like gVim.
|
|
|
|
|
|
|
|
|
|
If you ever happen to use a certain colorscheme in Vim running in a terminal
|
|
|
|
|
emulator and the colors don't look like the colors in the screenshot at all,
|
|
|
|
|
chances are that the colorscheme only defined colors for the GUI.
|
|
|
|
|
|
|
|
|
|
Here's a list of commonly used colorschemes:
|
|
|
|
|
|
|
|
|
|
- [base16](https://github.com/chriskempson/base16-vim)
|
|
|
|
|
- [gotham](https://github.com/whatyouhide/vim-gotham)
|
|
|
|
|
- [gruvbox](https://github.com/morhetz/gruvbox)
|
|
|
|
|
- [jellybeans](https://github.com/nanotech/jellybeans.vim)
|
|
|
|
|
- [molokai](https://github.com/tomasr/molokai)
|
|
|
|
|
- [railscasts](https://github.com/jpo/vim-railscasts-theme)
|
|
|
|
|
- [solarized](https://github.com/altercation/vim-colors-solarized) (or a lighter variant of it: [flattened](https://github.com/romainl/flattened))
|
|
|
|
|
- [vividchalk](https://github.com/tpope/vim-vividchalk)
|
|
|
|
|
|
|
|
|
|
I use gruvbox for the GUI and [janah](https://github.com/mhinz/vim-janah) for
|
|
|
|
|
the terminal.
|
|
|
|
|
|
|
|
|
|
## Basics
|
|
|
|
|
|
2016-01-04 18:00:36 +01:00
|
|
|
#### Managing plugins
|
|
|
|
|
|
|
|
|
|
[Pathogen](https://github.com/tpope/vim-pathogen) was the first popular tool for
|
|
|
|
|
managing plugins. Actually it just adjusts the _runtimepath_ (`:h 'rtp'`) to
|
|
|
|
|
include all the things put under a certain directory. You have have to clone the
|
|
|
|
|
repositories of the plugins there yourself.
|
|
|
|
|
|
|
|
|
|
Real plugin managers expose commands that help you installing and updating
|
|
|
|
|
plugins from within Vim. Hereinafter is a list of commonly used plugin managers
|
|
|
|
|
in alphabetic sequence:
|
|
|
|
|
|
|
|
|
|
- [neobundle](https://github.com/Shougo/neobundle.vim)
|
|
|
|
|
- [plug](https://github.com/junegunn/vim-plug)
|
|
|
|
|
- [vim-addon-manager](https://github.com/MarcWeber/vim-addon-manager)
|
|
|
|
|
- [vundle](https://github.com/VundleVim/Vundle.vim)
|
|
|
|
|
|
|
|
|
|
Plug is my favorite, but your mileage may vary.
|
