1. sirex
  2. vimpire


Shrikant Sharat Kandula  committed 4fced54

Added command-t example for using the Run directives, and some more description

  • Participants
  • Parent commits 85a5ee3
  • Branches default

Comments (0)

Files changed (1)


View file
 vcs from git or hg, and is correct most of the time, but if you want to specify it
 yourself, do so as
-	" Bundle: my-strange-url-from-which-no-one-can-tell-the-vcs with git
+    " Bundle: my-strange-url-from-which-no-one-can-tell-the-vcs with git
 There, that `with git` in the end is what tells Vimpire what vcs to use. Neat eh?
 You may also include a `Run` directive below the `Bundle` directive to run a command
 after getting/updating the corresponding bundle. Note that this command will be run
-with the plugin's directory as the pwd. For example
+with the plugin's directory as the pwd. For example, to compile Command-T plugin,
     " Bundle: git://github.com/tpope/vim-pathogen.git
-    " Run: ls -lh
+    " Run: cd ruby/command-t
+    " Run: ruby extconf.rb && make
-Deleting plugins is still experimental, but adding new ones and updating (pull) ing
-them works just fine.
+Note: If a run directive points to a `cd` command, like the 2nd line above, it is not
+sent to the shell. It is natively interpreted by vimpire, and does NOT have all the
+advanced functionality of the `cd` command in a shell. So, things like `cd -` do not work.
+This should not affect for most users, though.
+If a bundle entry is deleted, or a directory exists in the bundle directory, without a
+corresponding entry in the vimrc file, it will be deleted. Deleting plugins is still
+experimental, but if it does not work, you may manually delete the plugin directory in the
+bundle directory.
 Report any issues whatsoever :)