RubyGems - angry_mob_common_targets - Versions diffs - 0.1.0 - Mend

angry_mob_common_targets 0.1.0

Files changed (104) hide show

data/LICENSE +21 -0
data/README.md +38 -0
data/lib/common_mob.rb +9 -0
data/lib/common_mob/digest.rb +43 -0
data/lib/common_mob/erb.rb +72 -0
data/lib/common_mob/file.rb +55 -0
data/lib/common_mob/patch.rb +51 -0
data/lib/common_mob/resource_locator.rb +9 -0
data/lib/common_mob/shell.rb +323 -0
data/lib/common_mob/template.rb +23 -0
data/lib/common_mob/version.rb +3 -0
data/targets/crontab_patch.rb +37 -0
data/targets/extract.rb +40 -0
data/targets/fetch.rb +40 -0
data/targets/files.rb +244 -0
data/targets/git.rb +84 -0
data/targets/group.rb +33 -0
data/targets/packages.rb +94 -0
data/targets/ruby.rb +13 -0
data/targets/services.rb +184 -0
data/targets/shell.rb +43 -0
data/targets/user.rb +108 -0
data/vendor/mustache/CONTRIBUTORS +9 -0
data/vendor/mustache/HISTORY.md +135 -0
data/vendor/mustache/LICENSE +20 -0
data/vendor/mustache/README.md +405 -0
data/vendor/mustache/Rakefile +103 -0
data/vendor/mustache/benchmarks/complex.erb +15 -0
data/vendor/mustache/benchmarks/complex.haml +12 -0
data/vendor/mustache/benchmarks/helper.rb +20 -0
data/vendor/mustache/benchmarks/simple.erb +5 -0
data/vendor/mustache/benchmarks/speed.rb +78 -0
data/vendor/mustache/bin/mustache +90 -0
data/vendor/mustache/contrib/mustache-mode.el +278 -0
data/vendor/mustache/contrib/mustache.vim +69 -0
data/vendor/mustache/examples/hash.rb +16 -0
data/vendor/mustache/examples/hash.yml +5 -0
data/vendor/mustache/examples/projects.mustache +26 -0
data/vendor/mustache/examples/projects.yml +28 -0
data/vendor/mustache/examples/self.mustache +4 -0
data/vendor/mustache/examples/self.yml +3 -0
data/vendor/mustache/examples/simple.mustache +10 -0
data/vendor/mustache/examples/simple.rb +24 -0
data/vendor/mustache/lib/mustache.rb +358 -0
data/vendor/mustache/lib/mustache/context.rb +108 -0
data/vendor/mustache/lib/mustache/generator.rb +160 -0
data/vendor/mustache/lib/mustache/parser.rb +230 -0
data/vendor/mustache/lib/mustache/sinatra.rb +180 -0
data/vendor/mustache/lib/mustache/template.rb +59 -0
data/vendor/mustache/lib/mustache/version.rb +3 -0
data/vendor/mustache/lib/rack/bug/panels/mustache_panel.rb +81 -0
data/vendor/mustache/lib/rack/bug/panels/mustache_panel/mustache_extension.rb +27 -0
data/vendor/mustache/lib/rack/bug/panels/mustache_panel/view.mustache +46 -0
data/vendor/mustache/man/mustache.1 +180 -0
data/vendor/mustache/man/mustache.1.html +204 -0
data/vendor/mustache/man/mustache.1.ron +127 -0
data/vendor/mustache/man/mustache.5 +576 -0
data/vendor/mustache/man/mustache.5.html +415 -0
data/vendor/mustache/man/mustache.5.ron +324 -0
data/vendor/mustache/mustache.gemspec +32 -0
data/vendor/mustache/test/autoloading_test.rb +52 -0
data/vendor/mustache/test/fixtures/comments.mustache +1 -0
data/vendor/mustache/test/fixtures/comments.rb +14 -0
data/vendor/mustache/test/fixtures/complex_view.mustache +17 -0
data/vendor/mustache/test/fixtures/complex_view.rb +34 -0
data/vendor/mustache/test/fixtures/crazy_recursive.mustache +9 -0
data/vendor/mustache/test/fixtures/crazy_recursive.rb +31 -0
data/vendor/mustache/test/fixtures/delimiters.mustache +8 -0
data/vendor/mustache/test/fixtures/delimiters.rb +23 -0
data/vendor/mustache/test/fixtures/double_section.mustache +7 -0
data/vendor/mustache/test/fixtures/double_section.rb +14 -0
data/vendor/mustache/test/fixtures/escaped.mustache +1 -0
data/vendor/mustache/test/fixtures/escaped.rb +14 -0
data/vendor/mustache/test/fixtures/inner_partial.mustache +1 -0
data/vendor/mustache/test/fixtures/inner_partial.txt +1 -0
data/vendor/mustache/test/fixtures/inverted_section.mustache +7 -0
data/vendor/mustache/test/fixtures/inverted_section.rb +14 -0
data/vendor/mustache/test/fixtures/lambda.mustache +7 -0
data/vendor/mustache/test/fixtures/lambda.rb +31 -0
data/vendor/mustache/test/fixtures/namespaced.mustache +1 -0
data/vendor/mustache/test/fixtures/namespaced.rb +25 -0
data/vendor/mustache/test/fixtures/nested_objects.mustache +17 -0
data/vendor/mustache/test/fixtures/nested_objects.rb +35 -0
data/vendor/mustache/test/fixtures/node.mustache +8 -0
data/vendor/mustache/test/fixtures/partial_with_module.mustache +3 -0
data/vendor/mustache/test/fixtures/partial_with_module.rb +37 -0
data/vendor/mustache/test/fixtures/passenger.conf +5 -0
data/vendor/mustache/test/fixtures/passenger.rb +27 -0
data/vendor/mustache/test/fixtures/recursive.mustache +4 -0
data/vendor/mustache/test/fixtures/recursive.rb +14 -0
data/vendor/mustache/test/fixtures/simple.mustache +5 -0
data/vendor/mustache/test/fixtures/simple.rb +26 -0
data/vendor/mustache/test/fixtures/template_partial.mustache +2 -0
data/vendor/mustache/test/fixtures/template_partial.rb +18 -0
data/vendor/mustache/test/fixtures/template_partial.txt +4 -0
data/vendor/mustache/test/fixtures/unescaped.mustache +1 -0
data/vendor/mustache/test/fixtures/unescaped.rb +14 -0
data/vendor/mustache/test/fixtures/utf8.mustache +3 -0
data/vendor/mustache/test/fixtures/utf8_partial.mustache +1 -0
data/vendor/mustache/test/helper.rb +7 -0
data/vendor/mustache/test/mustache_test.rb +536 -0
data/vendor/mustache/test/parser_test.rb +54 -0
data/vendor/mustache/test/partial_test.rb +168 -0
metadata +167 -0

data/vendor/mustache/man/mustache.1.html ADDED

@@ -0,0 +1,204 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.5'>
+  <title>mustache(1) -- Mustache processor</title>
+  <style type='text/css'>
+    body {margin:0}
+    #man, #man code, #man pre, #man tt, #man kbd, #man samp {
+      font-family:consolas,monospace;
+      font-size:16px;
+      line-height:1.3;
+      color:#343331;
+      background:#fff; }
+    #man { max-width:89ex; text-align:justify; margin:0 25px 25px 25px }
+    #man h1, #man h2, #man h3 { color:#232221;clear:left }
+    #man h1 { font-size:28px; margin:15px 0 30px 0; text-align:center }
+    #man h2 { font-size:18px; margin-bottom:0; margin-top:10px; line-height:1.3; }
+    #man h3 { font-size:16px; margin:0 0 0 4ex; }
+    #man p, #man ul, #man ol, #man dl, #man pre { margin:0 0 18px 0; }
+    #man pre {
+      color:#333231;
+      background:#edeceb;
+      padding:5px 7px;
+      margin:0px 0 20px 0;
+      border-left:2ex solid #ddd}
+    #man pre + h2, #man pre + h3 {
+      margin-top:22px;
+    }
+    #man h2 + pre, #man h3 + pre {
+      margin-top:5px;
+    }
+    #man > p, #man > ul, #man > ol, #man > dl, #man > pre { margin-left:8ex; }
+    #man dt { margin:0; clear:left }
+    #man dt.flush { float:left; width:8ex }
+    #man dd { margin:0 0 0 9ex }
+    #man code, #man strong, #man b { font-weight:bold; color:#131211; }
+    #man pre code { font-weight:normal; color:#232221; background:inherit }
+    #man em, var, u {
+      font-style:normal; color:#333231; border-bottom:1px solid #999; }
+    #man h1.man-title { display:none; }
+    #man ol.man, #man ol.man li { margin:2px 0 10px 0; padding:0;
+      float:left; width:33%; list-style-type:none;
+      text-transform:uppercase; font-size:18px; color:#999;
+      letter-spacing:1px;}
+    #man ol.man { width:100%; }
+    #man ol.man li.tl { text-align:left }
+    #man ol.man li.tc { text-align:center;letter-spacing:4px }
+    #man ol.man li.tr { text-align:right }
+    #man ol.man a { color:#999 }
+    #man ol.man a:hover { color:#333231 }
+  </style>
+</head>
+<body>
+<div id='man'>
+<h1 class='man-title'>mustache(1)</h1>
+<ol class='head man'>
+  <li class='tl'>mustache(1)</li>
+  <li class='tc'>Mustache Manual</li>
+  <li class='tr'>mustache(1)</li>
+</ol>
+<h2 id='NAME'>NAME</h2>
+<p><code>mustache</code> -- Mustache processor</p>
+<h2>SYNOPSIS</h2>
+<pre><code>mustache &lt;YAML> &lt;FILE>
+mustache --compile &lt;FILE>
+mustache --tokens &lt;FILE>
+</code></pre>
+<h2>DESCRIPTION</h2>
+<p>Mustache is a logic-less templating system for HTML, config files,
+anything.</p>
+<p>The <code>mustache</code> command processes a Mustache template preceded by YAML
+frontmatter from standard input and prints one or more documents to
+standard output.</p>
+<p>YAML frontmatter beings with <code>---</code> on a single line, followed by YAML,
+ending with another <code>---</code> on a single line, e.g.</p>
+<pre><code>---
+names: [ {name: chris}, {name: mark}, {name: scott} ]
+---
+</code></pre>
+<p>If you are unfamiliar with YAML, it is a superset of JSON. Valid JSON
+should work fine.</p>
+<p>After the frontmatter should come any valid Mustache template. See
+mustache(5) for an overview of Mustache templates.</p>
+<p>For example:</p>
+<pre><code>{{#names}}
+  Hi {{name}}!
+{{/names}}
+</code></pre>
+<p>Now let's combine them.</p>
+<pre><code>$ cat data.yml
+---
+names: [ {name: chris}, {name: mark}, {name: scott} ]
+---
+$ cat template.mustache
+{{#names}}
+  Hi {{name}}!
+{{/names}}
+$ cat data.yml template.mustache | mustache
+Hi chris!
+Hi mark!
+Hi scott!
+</code></pre>
+<p>If you provide multiple YAML documents (as delimited by <code>---</code>), your
+template will be rendered multiple times. Like a mail merge.</p>
+<p>For example:</p>
+<pre><code>$ cat data.yml
+---
+name: chris
+---
+name: mark
+---
+name: scott
+---
+$ cat template.mustache
+Hi {{name}}!
+$ cat data.yml template.mustache | mustache
+Hi chris!
+Hi mark!
+Hi scott!
+</code></pre>
+<h2>OPTIONS</h2>
+<p>By default <code>mustache</code> will try to render a Mustache template using the
+YAML frontmatter you provide. It can do a few other things, however.</p>
+<dl>
+<dt><code>-c</code>, <code>--compile</code></dt><dd><p>Print the compiled Ruby version of a given template. This is the
+code that is actually used when rendering a template into a
+string. Useful for debugging but only if you are familiar with
+Mustache's internals.</p></dd>
+<dt><code>-t</code>, <code>--tokens</code></dt><dd><p>Print the tokenized form of a given Mustache template. This can be
+used to understand how Mustache parses a template. The tokens are
+handed to a generator which compiles them into a Ruby
+string. Syntax errors and confused tags, therefor, can probably be
+identified by examining the tokens produced.</p></dd>
+</dl>
+<h2>INSTALLATION</h2>
+<p>If you have RubyGems installed:</p>
+<pre><code>gem install mustache
+</code></pre>
+<h2>EXAMPLES</h2>
+<pre><code>$ mustache data.yml template.mustache
+$ cat data.yml | mustache - template.mustache
+$ mustache -c template.mustache
+$ cat &lt;&lt;data | ruby mustache - template.mustache
+---
+name: Bob
+age: 30
+---
+data
+</code></pre>
+<h2>COPYRIGHT</h2>
+<p>Mustache is Copyright (C) 2009 Chris Wanstrath</p>
+<p>Original CTemplate by Google</p>
+<h2>SEE ALSO</h2>
+<p>mustache(5), mustache(7), gem(1),
+<a href="http://mustache.github.com/">http://mustache.github.com/</a></p>
+<ol class='foot man'>
+  <li class='tl'>DEFUNKT</li>
+  <li class='tc'>May 2010</li>
+  <li class='tr'>mustache(1)</li>
+</ol>
+</div>
+</body>
+</html>

data/vendor/mustache/man/mustache.1.ron ADDED

@@ -0,0 +1,127 @@
+mustache(1) -- Mustache processor
+=================================
+## SYNOPSIS
+    mustache <YAML> <FILE>
+    mustache --compile <FILE>
+    mustache --tokens <FILE>
+## DESCRIPTION
+Mustache is a logic-less templating system for HTML, config files,
+anything.
+The `mustache` command processes a Mustache template preceded by YAML
+frontmatter from standard input and prints one or more documents to
+standard output.
+YAML frontmatter beings with `---` on a single line, followed by YAML,
+ending with another `---` on a single line, e.g.
+    ---
+    names: [ {name: chris}, {name: mark}, {name: scott} ]
+    ---
+If you are unfamiliar with YAML, it is a superset of JSON. Valid JSON
+should work fine.
+After the frontmatter should come any valid Mustache template. See
+mustache(5) for an overview of Mustache templates.
+For example:
+    {{#names}}
+      Hi {{name}}!
+    {{/names}}
+Now let's combine them.
+    $ cat data.yml
+    ---
+    names: [ {name: chris}, {name: mark}, {name: scott} ]
+    ---
+    $ cat template.mustache
+    {{#names}}
+      Hi {{name}}!
+    {{/names}}
+    $ cat data.yml template.mustache | mustache
+    Hi chris!
+    Hi mark!
+    Hi scott!
+If you provide multiple YAML documents (as delimited by `---`), your
+template will be rendered multiple times. Like a mail merge.
+For example:
+    $ cat data.yml
+    ---
+    name: chris
+    ---
+    name: mark
+    ---
+    name: scott
+    ---
+    $ cat template.mustache
+    Hi {{name}}!
+    $ cat data.yml template.mustache | mustache
+    Hi chris!
+    Hi mark!
+    Hi scott!
+## OPTIONS
+By default `mustache` will try to render a Mustache template using the
+YAML frontmatter you provide. It can do a few other things, however.
+  * `-c`, `--compile`:
+    Print the compiled Ruby version of a given template. This is the
+    code that is actually used when rendering a template into a
+    string. Useful for debugging but only if you are familiar with
+    Mustache's internals.
+  * `-t`, `--tokens`:
+    Print the tokenized form of a given Mustache template. This can be
+    used to understand how Mustache parses a template. The tokens are
+    handed to a generator which compiles them into a Ruby
+    string. Syntax errors and confused tags, therefor, can probably be
+    identified by examining the tokens produced.
+## INSTALLATION
+If you have RubyGems installed:
+    gem install mustache
+## EXAMPLES
+    $ mustache data.yml template.mustache
+    $ cat data.yml | mustache - template.mustache
+    $ mustache -c template.mustache
+    $ cat <<data | ruby mustache - template.mustache
+    ---
+    name: Bob
+    age: 30
+    ---
+    data
+## COPYRIGHT
+Mustache is Copyright (C) 2009 Chris Wanstrath
+Original CTemplate by Google
+## SEE ALSO
+mustache(5), mustache(7), gem(1),
+<http://mustache.github.com/>

data/vendor/mustache/man/mustache.5 ADDED

@@ -0,0 +1,576 @@
+.\" generated with Ronn/v0.5
+.\" http://github.com/rtomayko/ronn/
+.
+.TH "MUSTACHE" "5" "May 2010" "DEFUNKT" "Mustache Manual"
+.
+.SH "NAME"
+\fBmustache\fR \-\- Logic\-less templates.
+.
+.SH "SYNOPSIS"
+A typical Mustache template:
+.
+.IP "" 4
+.
+.nf
+Hello {{name}}
+You have just won {{value}} dollars!
+{{#in_ca}}
+Well, {{taxed_value}} dollars, after taxes.
+{{/in_ca}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Given the following hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "name": "Chris",
+  "value": 10000,
+  "taxed_value": 10000 \- (10000 * 0.4),
+  "in_ca": true
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Will produce the following:
+.
+.IP "" 4
+.
+.nf
+Hello Chris
+You have just won 10000 dollars!
+Well, 6000.0 dollars, after taxes.
+.
+.fi
+.
+.IP "" 0
+.
+.SH "DESCRIPTION"
+Mustache can be used for HTML, config files, source code \-
+anything. It works by expanding tags in a template using values
+provided in a hash or object.
+.
+.P
+We call it "logic\-less" because there are no if statements, else
+clauses, or for loops. Instead there are only tags. Some tags are
+replaced with a value, some nothing, and others a series of
+values. This document explains the different types of Mustache tags.
+.
+.SH "TAG TYPES"
+Tags are indicated by the double mustaches. \fB{{person}}\fR is a tag, as
+is \fB{{#person}}\fR. In both examples, we'd refer to \fBperson\fR as the key
+or tag key. Let's talk about the different types of tags.
+.
+.SS "Variables"
+The most basic tag type is the variable. A \fB{{name}}\fR tag in a basic
+template will try to find the \fBname\fR key in the current context. If
+there is no \fBname\fR key, nothing will be rendered.
+.
+.P
+All variables are HTML escaped by default. If you want to return
+unescaped HTML, use the triple mustache: \fB{{{name}}}\fR.
+.
+.P
+You can also use \fB&\fR to unescape a variable: \fB{{& name}}\fR. This may be
+useful when changing delimiters (see "Set Delimiter" below).
+.
+.P
+By default a variable "miss" returns an empty string. This can usually
+be configured in your Mustache library. The Ruby version of Mustache
+supports raising an exception in this situation, for instance.
+.
+.P
+Template:
+.
+.IP "" 4
+.
+.nf
+* {{name}}
+* {{age}}
+* {{company}}
+* {{{company}}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "name": "Chris",
+  "company": "<b>GitHub</b>"
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Output:
+.
+.IP "" 4
+.
+.nf
+* Chris
+*
+* &lt;b&gt;GitHub&lt;/b&gt;
+* <b>GitHub</b>
+.
+.fi
+.
+.IP "" 0
+.
+.SS "Sections"
+Sections render blocks of text one or more times, depending on the
+value of the key in the current context.
+.
+.P
+A section begins with a pound and ends with a slash. That is, \fB{{#person}}\fR begins a "person" section while \fB{{/person}}\fR ends it.
+.
+.P
+The behavior of the section is determined by the value of the key.
+.
+.P
+\fBFalse Values or Empty Lists\fR
+.
+.P
+If the \fBperson\fR key exists and has a value of false or an empty
+list, the HTML between the pound and slash will not be displayed.
+.
+.P
+Template:
+.
+.IP "" 4
+.
+.nf
+Shown.
+{{#nothin}}
+  Never shown!
+{{/nothin}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "person": true,
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Output:
+.
+.IP "" 4
+.
+.nf
+Shown.
+.
+.fi
+.
+.IP "" 0
+.
+.P
+\fBNon\-Empty Lists\fR
+.
+.P
+If the \fBperson\fR key exists and has a non\-false value, the HTML between
+the pound and slash will be rendered and displayed one or more times.
+.
+.P
+When the value is a non\-empty list, the text in the block will be
+displayed once for each item in the list. The context of the block
+will be set to the current item for each iteration. In this way we can
+loop over collections.
+.
+.P
+Template:
+.
+.IP "" 4
+.
+.nf
+{{#repo}}
+  <b>{{name}}</b>
+{{/repo}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "repo": [
+    { "name": "resque" },
+    { "name": "hub" },
+    { "name": "rip" },
+  ]
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Output:
+.
+.IP "" 4
+.
+.nf
+<b>resque</b>
+<b>hub</b>
+<b>rip</b>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+\fBLambdas\fR
+.
+.P
+When the value is a callable object, such as a function or lambda, the
+object will be invoked and passed the block of text. The text passed
+is the literal block, unrendered. \fB{{tags}}\fR will not have been expanded
+\- the lambda should do that on its own. In this way you can implement
+filters or caching.
+.
+.P
+Template:
+.
+.IP "" 4
+.
+.nf
+{{#wrapped}}
+  {{name}} is awesome.
+{{/wrapped}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "name": "Willy",
+  "wrapped": function() {
+    return function(text) {
+      return "<b>" + render(text) + "</b>"
+    }
+  }
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Output:
+.
+.IP "" 4
+.
+.nf
+<b>Willy is awesome.</b>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+\fBNon\-False Values\fR
+.
+.P
+When the value is non\-false but not a list, it will be used as the
+context for a single rendering of the block.
+.
+.P
+Template:
+.
+.IP "" 4
+.
+.nf
+{{#person?}}
+  Hi {{name}}!
+{{/person?}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "person?": { "name": "Jon" }
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Output:
+.
+.IP "" 4
+.
+.nf
+Hi Jon!
+.
+.fi
+.
+.IP "" 0
+.
+.SS "Inverted Sections"
+An inverted section begins with a caret (hat) and ends with a
+slash. That is \fB{{^person}}\fR begins a "person" inverted section while \fB{{/person}}\fR ends it.
+.
+.P
+While sections can be used to render text one or more times based on the
+value of the key, inverted sections may render text once based
+on the inverse value of the key. That is, they will be rendered
+if the key doesn't exist, is false, or is an empty list.
+.
+.P
+Template:
+.
+.IP "" 4
+.
+.nf
+{{#repo}}
+  <b>{{name}}</b>
+{{/repo}}
+{{^repo}}
+  No repos :(
+{{/repo}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "repo": []
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Output:
+.
+.IP "" 4
+.
+.nf
+No repos :(
+.
+.fi
+.
+.IP "" 0
+.
+.SS "Comments"
+Comments begin with a bang and are ignored. The following template:
+.
+.IP "" 4
+.
+.nf
+<h1>Today{{! ignore me }}.</h1>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Will render as follows:
+.
+.IP "" 4
+.
+.nf
+<h1>Today.</h1>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Comments may contain newlines.
+.
+.SS "Partials"
+Partials begin with a greater than sign, like \fB{{> box}}\fR.
+.
+.P
+Partials are rendered at runtime (as opposed to compile time), so
+recursive partials are possible. Just avoid infinite loops.
+.
+.P
+They also inherit the calling context. Whereas in ERB you may have
+this:
+.
+.IP "" 4
+.
+.nf
+<%= partial :next_more, :start => start, :size => size %>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Mustache requires only this:
+.
+.IP "" 4
+.
+.nf
+{{> next_more}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Why? Because the \fBnext_more.mustache\fR file will inherit the \fBsize\fR and \fBstart\fR methods from the calling context.
+.
+.P
+In this way you may want to think of partials as includes, or template
+expansion, even though it's not literally true.
+.
+.P
+For example, this template and partial:
+.
+.IP "" 4
+.
+.nf
+base.mustache:
+<h2>Names</h2>
+{{#names}}
+  {{> user}}
+{{/names}}
+user.mustache:
+<strong>{{name}}</strong>
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Can be thought of as a single, expanded template:
+.
+.IP "" 4
+.
+.nf
+<h2>Names</h2>
+{{#names}}
+  <strong>{{name}}</strong>
+{{/names}}
+.
+.fi
+.
+.IP "" 0
+.
+.SS "Set Delimiter"
+Set Delimiter tags start with an equal sign and change the tag
+delimiters from \fB{{\fR and \fB}}\fR to custom strings.
+.
+.P
+Consider the following contrived example:
+.
+.IP "" 4
+.
+.nf
+* {{default_tags}}
+{{=<% %>=}}
+* <% erb_style_tags %>
+<%={{ }}=%>
+* {{ default_tags_again }}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Here we have a list with three items. The first item uses the default
+tag style, the second uses erb style as defined by the Set Delimiter
+tag, and the third returns to the default style after yet another Set
+Delimiter declaration.
+.
+.P
+According to \fIctemplates\fR, this "is useful for languages like TeX, where
+double\-braces may occur in the text and are awkward to use for
+markup."
+.
+.P
+Custom delimiters may not contain whitespace or the equals sign.
+.
+.SH "COPYRIGHT"
+Mustache is Copyright (C) 2009 Chris Wanstrath
+.
+.P
+Original CTemplate by Google
+.
+.SH "SEE ALSO"
+mustache(1), mustache(7), \fIhttp://mustache.github.com/\fR