Join the DZone community and get the full member experience.
Join For FreeAccess over 20 APIs and mobile SDKs, up to 250k transactions free with no credit card required
I have been in and out of using vim a few times now. As I understand it, this is usually the case when transitioning to using vim fulltime.
One rule I found especially useful when learning vim and the massive plug-in universe is to write your own vimrc file. This file contains all the settings for your vim editor.
This has two benefits:
- You know all the plug-ins you use.
- You can also fix things when they break.
A new user’s vimrc should be as minimal as possible.
I tweeted the following screenshot last night
In the past, I found this extremely frustrating and annoying to get this correctly setup vim how I liked it. I was especially patient last night and managed to get something that I didn’t think was completely ugly.
You can find my vimrc file here.
Here is a list of plugins I have installed:
- Gundo
- vim-powerline
- fugitive
- pathogen
- python-mode
- NerdTree
- tagbar
You can find my dotfiles here. If anyone has any questions hit me up on twitter.
#1 for location developers in quality, price and choice, switch to HERE.
Like This Article? Read More From DZone
Published at DZone with permission of Mahdi Yusuf , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}