# HG changeset patch
# User Steve Losh <steve@dwaiter.com>
# Date 1285089532 14400
# Node ID e522010500abe1731ce42a435f41e641036a9af9
# Parent  4418d4cb09e49516be198ae9492f40b6d17ae9ab# Parent  907ff6053251fe49413fa7dddd495cb2de5f59ad
Merge.

diff -r 907ff6053251 -r e522010500ab content/blog/2010/09/coming-home-to-vim.html
--- a/content/blog/2010/09/coming-home-to-vim.html	Mon Sep 20 22:02:33 2010 -0400
+++ b/content/blog/2010/09/coming-home-to-vim.html	Tue Sep 21 13:18:52 2010 -0400
@@ -279,15 +279,18 @@
 
     :::vim
     filetype off
+    call pathogen#runtime_append_all_bundles()
     filetype plugin indent on
 
     set nocompatible
 
     set modelines=0
 
-I'm not entirely sure what the `filetype` lines do. I've read that they're
-necessary and so far I haven't had problems.  There's only so much time that
-I want to spend on digging into Vim's internals.
+The `filetype` and `call` lines are for loading Pathogen, which is described in
+the bundles section. See [Pathogen's docs][pathogendocs] to learn about why the
+first `filetype` line is there.
+
+[pathogendocs]: http://www.vim.org/scripts/script.php?script_id=2332
 
 `set nocompatible` gets rid of all the crap that Vim does to be vi compatible.
 It's 2010 -- we don't need to be compatible with vi at the expense of