Skip to content

rfc1459/vimfiles

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

~/.vim

Contents of my ~/.vim directory, take two.

Why did you start over?

Because there was so much cruft that I ended up nuking half the repo, so...

Vim

Personally, I recommend you use gVim on Windows and plain vim with a decent terminal emulator everywhere else. xfce4-terminal is a good starting point.

You can download vim from:

Usage

Clone this repo into your home directory either as .vim (linux/mac) or vimfiles (Windows). Such as:

git clone https://github.com/rfc1459/vimfiles.git ~/.vim

Activating the new configuration

After cloning, you should create a new .vimrc file in your home directory that loads the pre-configured one that comes bundled in this package. On Linux, a symbolic link will suffice:

$ ln -s ~/.vim/vimrc .vimrc
$ ln -s ~/.vim/gvimrc .gvimrc

On Windows, you should create a _vimrc and a _gvimrc in your profile's home directory and add the following line inside:

_vimrc:

source ~/vimfiles/vimrc

_gvimrc:

source ~/vimfiles/gvimrc

Note

On Vim 7.4 or later you can safely skip the previous step altogether.

Help Tags

At first usage of vim, type ":" while in command mode and then execute:

Helptags

This will make the plugins documentation available upon :help

Dependencies

You will need the following software on your system:

  • Ncurses-term (in Linux only)

On Debian derivatives, for example, you will have to do:

apt-get install ncurses-term

Vim? WTF?

Visit the following sites to learn more about Vim:

There are many sites teaching Vim, if you know of any other that are easy to follow for newcomers, let me know.

Credits

  • Letting me know that versioning ~/.vim was a good idea: @vjt
  • Inspiration for cleanup: @mislav
  • Ditching submodules for subtrees: @durdn
  • Vim demigod: @tpope

Releases

No releases published

Packages

No packages published