vim-bootstrap | Vim Bootstrap is a generator that provides a simple method | Code Editor library

This vimrc file is using vim-plug to manage plugins.

Quick overview of vim-plug:

• Use Plug {github-user}/{repo} to use the specified plugin repository
• Plug statement should be between call plug#begin() and call plug#end()
• plug#begin({dir}) can specify directory, {dir}, where vim-plug controlled plugins will live
• :PlugInstall will do any necessary fetching & installing of all defined plugins
• if executable('curl') check to make sure you have an executable curl program. This is used to download vim-plug

Much of this code is to make sure vim-plug is present and tries to install itself.

Personally, I feel like vim-bootstrap is a Vim distribution. I must warn you, it is very compelling to jump into Vim with a bunch of plugins and a customized vimrc file. However, I would advise you to avoid distributions and customized vimrc files. These distributions often make it feel like a different editor or sell you on the idea of these "must have" plugins. Often this causes newer Vim users to get confused where vanilla Vim ends and their plugins begin. When it comes to customizing Vim newer Vimmers often do not have the prerequisite knowledge needed to understand and maintain their distribution's vimrc setup. Instead I suggest slowly learning and building your own vimrc. Basically "sharpen the saw"

The best general advice is a simple one, "Sharpen the saw" from Bram's Seven habits essay. I also suggest Vimcasts blog post: On sharpening the saw.

Basically "sharpening the saw" can be summarized as:

Don't learn everything all at once, but learn a few things at a time. When you find an inefficiency look for ways to improve it. Repeat

I also recommend you use nearly blank vimrc. You should roughly understand each line in your vimrc. Use :help and google learn more.

General plugin advice:

• Slowly add a plugin or two when the need arises.
• Do not install a plugin without looking for a native solution first
• Must have good documentation
• Avoid plugins with many mappings
• If it doesn't feel Vim-like then avoid it
• Avoid if mappings doesn't work with the . command (may have to use repeat.vim)

• Vimcasts - Great articles and screencasts by Drew Neil, the author of Practical Vim.
• Derek Wyatt's Vim Videos - Good collection of Vim topics.
• Learn Vimscript the Hard Way - Steve Losh teaches how to customize Vim from the basics to the more advanced.

Read :help and try to make small incremental changes to your workflow.