From 78ea5a9f42b7fd8c5e8eebedfaef418fa2f003d4 Mon Sep 17 00:00:00 2001
From: Shrikant Sharat <shrikantsharat.k@gmail.com>
Date: Sat, 9 Jun 2012 20:59:23 +0530
Subject: [PATCH] Add notes on antigen-bundles command to README.

---
 README.mkd | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/README.mkd b/README.mkd
index e42138a..4d41bf8 100644
--- a/README.mkd
+++ b/README.mkd
@@ -139,6 +139,37 @@ from your shell environment. This allows you to install plugins on the fly and
 try them out. Of course if you want a bundle to be available every time you open
 a shell, put it in your `.zshrc`.
 
+## antigen-bundles
+
+If you have a fair number of bundles, using the `antigen-bundle` command can
+look cumbersome. You can use the `antigen-bundles` command to *bulk* define
+bundles instead of individual calls to `antigen-bundle`.
+
+Usage is pretty straightforward. Just pipe the bundle specifications, just as
+you would give to the `antigen-bundle` command, one per line, into the
+`antigen-bundles` command. The easiest way to do this, is using the heredoc
+syntax.
+
+    antigen-bundles <<EOF
+    # Guess what to install when running an unknown command.
+    command-not-found
+
+    # The heroku tool helper plugin.
+    heroku
+
+    EOF
+
+This is equivalent to
+
+    antigen-bundle command-not-found
+    antigen-bundle heroku
+
+Of course, as you can see, from the lines piped to `antigen-bundles`, empty
+lines and those starting with a `#` are ignored. The rest are passed to
+`antigen-bundle` without any quoting rules applied. They are actually `eval`-ed
+with the `antigen-bundle` command. See the source if you want to really
+understand how it works. Its a very small function.
+
 ## antigen-update
 
 This is something you might not want to put in your `.zshrc`. Instead, run it
-- 
2.0.0