Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
We want to unlock the full potential of vim. That's what set nocompatible does. It needs to be set before all other options.
- Loading branch information
0673f0c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(next step -->)
This is how it's gonna work: you'll see a description of what's happening in the commit message (that blue box up there!), a certain number of lines highlighted in green, and then some comments for clarification. This first commit is pretty boring--it gets better, trust me!
Note that we want to call this file
~/.vimrc
instead ofvimrc.vim
. I've named it accordingly so that GitHub syntax highlights it correctly, but you should change that name.0673f0c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
according to the OS, vimrc is not always under ~/.vimrc, therefore the most straightforward way to edit this file is to type the following command in vim or givm
0673f0c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose, but my original audience was a room of ~50 beginners. When in doubt, keep it simple. Thanks for pointing it out though!
0673f0c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nocompatible is default in vim now :)