commit 57dd83f505828fade84f9bc6ab51679b0fba8c19 parent bd0d5b5647d9ed4a1b6c3248337e793932a70dc6 Author: edvb54 <edvb54@gmail.com> Date: Fri, 20 Jun 2014 13:38:31 -0700 Add "Why You Should Use "set nocompatible"" to README.md Diffstat:
| README.md | | | 10 | ++++++++++ |
1 file changed, 10 insertions(+), 0 deletions(-)
diff --git a/README.md b/README.md @@ -44,6 +44,16 @@ Now refresh the folder: Please note that is has only been tested to work on Ubuntu. If you do not use Ubuntu this may not work. +## 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 and +not bee compatible with Vi. This is because if Vim sees a .vimrc file in +the home directory then it auto-magically 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. It is also a case of +better safe than sorry. + ##Contact Check out my website at [techandcode.com](http://techandcode.com) for more,