My vimrc is cleaner:<p><pre><code> $ cat ~/.vimrc
cat: /home/evanm/.vimrc: No such file or directory
</code></pre>
I mean, it's cool and all that you love your tools, but I suspect these sorts of blog posts are net harmful when you consider the number of people who will read it and take it as an opportunity to fiddle around with settings in a program as a way of further putting off making something meaningful.
To me, it really doesn't matter if you maintain your plugin settings in your .vimrc or in separate files, as long as it's well annotated and organized the way you like it.<p>Plus, all I have to do is track my .vimrc in my dotfiles repo and let Vundle manage my plugins for me.
I followed the modular init file approach at first, but keeping track of dependencies between different modules was a chore. Having all of my initialization code in a single file greatly simplifies maintenance: I could instantly tell what code runs before or after a certain line and I could easily navigate among sections of code and fold them based on headings.<p>Nowadays, my emacs init file is 239 kB. Is it messy? Yes, in some places, for customizations I don't care that much, it is, because each section I rely on constantly gets constantly refactored.<p>Modularization helps when you are going to share code among different projects, but your init file is a single project, what does splitting it buys you? Only increased complexity. Of course, as soon as functions get refactored and made more general and independent, they go into a module of their own.
<i>Remap caps-lock to escape</i><p>Ugh, why? Remapping caps-lock to Ctrl makes more sense to me. The Escape key is still in the upper-left, and banging somewhere in that vicinity usually hits it. Also Ctrl-C equals Escape in vim, so you still have quick access to it from the home row if you want.
But not the best: <a href="https://github.com/Diablo-D3/dot_vim" rel="nofollow">https://github.com/Diablo-D3/dot_vim</a><p>Edit: Woah, that guy needs to learn how to use Vundle and not embed third party files in his git repo, and let Vundle fetch it for him (look at mine for example)
I have my vimrc on github as well. It gets the job done for me. Keep in mind I'm far more of a sysadmin than a programmer.<p><a href="https://github.com/daniellockard/vimrc" rel="nofollow">https://github.com/daniellockard/vimrc</a>