RubyGems - zine_brewer - Versions diffs - 1.3.2 → 1.5.0 - Mend

zine_brewer 1.3.2 → 1.5.0

Files changed (801) hide show

data/vendor/bundle/ruby/2.7.0/gems/mustache-1.1.1/man/mustache.1.html ADDED

@@ -0,0 +1,213 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>mustache(1) - Mustache processor</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#INSTALLATION">INSTALLATION</a>
+    <a href="#EXAMPLES">EXAMPLES</a>
+    <a href="#COPYRIGHT">COPYRIGHT</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+  <ol class='man-decor man-head man head'>
+    <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 class="man-name">
+  <code>mustache</code> - <span class="man-whatis">Mustache processor</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+<pre><code>mustache &lt;YAML> &lt;FILE>
+mustache --compile &lt;FILE>
+mustache --tokens &lt;FILE>
+</code></pre>
+<h2 id="DESCRIPTION">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 begins 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
+<a class="man-ref" href="mustache.5.ronn.html">mustache<span class="s">(5)</span></a> 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}}
+$ mustache data.yml template.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}}!
+$ mustache data.yml template.mustache
+Hi chris!
+Hi mark!
+Hi scott!
+</code></pre>
+<h2 id="OPTIONS">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, therefore, can probably be
+identified by examining the tokens produced.</p></dd>
+</dl>
+<h2 id="INSTALLATION">INSTALLATION</h2>
+<p>If you have RubyGems installed:</p>
+<pre><code>gem install mustache
+</code></pre>
+<h2 id="EXAMPLES">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 id="COPYRIGHT">COPYRIGHT</h2>
+<p>Mustache is Copyright (C) 2009 Chris Wanstrath</p>
+<p>Original CTemplate by Google</p>
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+<p><a class="man-ref" href="mustache.5.ronn.html">mustache<span class="s">(5)</span></a>, <span class="man-ref">gem<span class="s">(1)</span></span>,
+<a href="http://mustache.github.io/" data-bare-link="true">http://mustache.github.io/</a></p>
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'>DEFUNKT</li>
+    <li class='tc'>November 2016</li>
+    <li class='tr'>mustache(1)</li>
+  </ol>
+  </div>
+</body>
+</html>

data/vendor/bundle/ruby/2.7.0/gems/mustache-1.1.1/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 begins 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}}
+    $ mustache data.yml template.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}}!
+    $ mustache data.yml template.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, therefore, 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), gem(1),
+<http://mustache.github.io/>

data/vendor/bundle/ruby/2.7.0/gems/mustache-1.1.1/man/mustache.5 ADDED

@@ -0,0 +1,539 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "MUSTACHE" "5" "November 2016" "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, the parent contexts will be checked recursively\. If the top context is reached and the \fBname\fR key is still not found, nothing will be rendered\.
+.
+.P
+All variables are HTML escaped by default\. If you want to return raw contents without escaping, use the triple mustache: \fB{{{name}}}\fR\.
+.
+.P
+You can also use \fB&\fR to return its raw contents: \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 zero 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\.
+{{#person}}
+  Never shown!
+{{/person}}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Hash:
+.
+.IP "" 4
+.
+.nf
+{
+  "person": false
+}
+.
+.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, render) {
+      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 zero 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 ctemplates \fIhttp://google\-ctemplate\.googlecode\.com/svn/trunk/doc/howto\.html\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), \fIhttp://mustache\.github\.io/\fR