title: Pros and cons for each vimrc cross-platform solution?
body: <p>When dealing with <code>.vimrc</code> configuration files in Linux and Windows (two systems I've been using so far) and trying to keep configurations cross-platform, I've found mainly two solutions:</p>
  
  <ol>
  <li><p>Create a new folder for vim files in <code>/home/user</code>, so both systems have the same vim dirname (instead of default <code>.vim</code> in linux and <code>vimfiles</code> in Windows), and use <code>set runtimepath</code> to get this new folder;</p>
  
  <p>set runtimepath=~/vim_local,$VIMRUNTIME
  source ~/vim_local/vimrc</p>
  
  <p><a href="http://amix.dk/blog/post/162" rel="nofollow noreferrer">Source</a></p></li>
  <li><p>Create a bunch of os conditions (like <code>has("32")</code>) in <code>.vimrc</code> when needed, based on platform or <a href="https://stackoverflow.com/questions/3289922/vimrc-to-be-cross-plataform-and-synced-with-dropbox/3291710#3291710">capabilities</a>, but keeping the original unix names and creating symlinks in Windows home folder to the original files (<code>vimfiles</code> to <code>.vim</code> somewhere, maybe a <code>.vim</code> dir in Windows home, or even a dropbox folder). (I haven't tested this approach in older Windows versions like XP).</p></li>
  </ol>
  
  <p>Which solution do you prefer, and why? What are the disadvantages from each solution? Which other solutions do you have? (You can post your own <code>.vimrc</code> here as well to discuss.)</p>
  
  <p>If you use some source control in your <code>.vimrc</code> configuration files, do you version your plugin files as well (so when "deploying" your config across computers, you only do a checkout/clone from your repository)? A lot of people are using <a href="http://www.vim.org/scripts/script.php?script_id=2332" rel="nofollow noreferrer">pathogen</a> and keeping each plugin inside it's own folder (usually a git repo from github). Does it make sense to version control a plugin that is already a repository from elsewhere?</p>