Unnamed repository; edit this file 'description' to name the repository.
git clone git://
Log | Files | Refs

commit 931c48de92b61ae8eb16a9bf322ac4793d666ab5
parent 632cb781256024232a5b191f4e877c83a4b377ee
Author: Ed van Bruggen <>
Date:   Tue, 29 Dec 2015 22:03:12 -0800


Diffstat: | 13+------------
1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/ b/ @@ -1,7 +1,7 @@ # ED's Dotfiles This is the place I use to store all my configuration files for programs such -as Vim, Bash, and Tmux. These files are designed to be used on Linux and most +as Vim, Bash, Tmux, etc. These files are designed to be used on Linux and most likely won't work on other machines. I recommend you not to just copy whole files, but instead copy one line at a time that you understand and slowly build up a huge file. This way you have a setup that fits you best. @@ -40,17 +40,6 @@ enter this into Vim: After it has finished installing you can exit the Vundle window and the plug-ins should be installed. -## Why You Should Use "set nocompatible" - -There is a lot of controversy over the use of `set nocompatible` in the Vim -world. This command makes Vim use the new features that they added, extending -Vi, thus not being compatible with it. However, people say this redundant -because if Vim sees a `.vimrc` file in the home directory then it automatically -sets no compatibility. But however, if you load a `.vimrc` using `vim -u -.new_vimrc` or `:so .new_vimrc` then it will load Vim being compatible with Vi, -if it does not contain `set nocompatible`. It is also a case of better safe -than sorry, adding one line of 16 characters to your `.vimrc` file won't hurt. - ##Contact If you have any questions or comments please contact me at or