mirror of
https://github.com/flokoe/bash-hackers-wiki.git
synced 2024-11-25 07:43:42 +01:00
86 lines
60 KiB
HTML
86 lines
60 KiB
HTML
|
<!doctype html><html lang=en class=no-js> <head><meta charset=utf-8><meta name=viewport content="width=device-width,initial-scale=1"><link href=https://flokoe.github.io/bash-hackers-wiki/syntax/basicgrammar/ rel=canonical><link href=../arrays/ rel=prev><link href=../pattern/ rel=next><link rel=icon href=../../assets/images/favicon.png><meta name=generator content="mkdocs-1.6.1, mkdocs-material-9.5.44"><title>Basic grammar rules of Bash - The Bash Hackers Wiki</title><link rel=stylesheet href=../../assets/stylesheets/main.0253249f.min.css><link rel=stylesheet href=../../assets/stylesheets/palette.06af60db.min.css><link rel=preconnect href=https://fonts.gstatic.com crossorigin><link rel=stylesheet href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback"><style>:root{--md-text-font:"Roboto";--md-code-font:"Roboto Mono"}</style><script>__md_scope=new URL("../..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script></head> <body dir=ltr data-md-color-scheme=default data-md-color-primary=indigo data-md-color-accent=indigo> <input class=md-toggle data-md-toggle=drawer type=checkbox id=__drawer autocomplete=off> <input class=md-toggle data-md-toggle=search type=checkbox id=__search autocomplete=off> <label class=md-overlay for=__drawer></label> <div data-md-component=skip> <a href=#basic-grammar-rules-of-bash class=md-skip> Skip to content </a> </div> <div data-md-component=announce> </div> <header class=md-header data-md-component=header> <nav class="md-header__inner md-grid" aria-label=Header> <a href=../.. title="The Bash Hackers Wiki" class="md-header__button md-logo" aria-label="The Bash Hackers Wiki" data-md-component=logo> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg> </a> <label class="md-header__button md-icon" for=__drawer> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M3 6h18v2H3zm0 5h18v2H3zm0 5h18v2H3z"/></svg> </label> <div class=md-header__title data-md-component=header-title> <div class=md-header__ellipsis> <div class=md-header__topic> <span class=md-ellipsis> The Bash Hackers Wiki </span> </div> <div class=md-header__topic data-md-component=header-topic> <span class=md-ellipsis> Basic grammar rules of Bash </span> </div> </div> </div> <form class=md-header__option data-md-component=palette> <input class=md-option data-md-color-media data-md-color-scheme=default data-md-color-primary=indigo data-md-color-accent=indigo aria-label="Switch to dark mode" type=radio name=__palette id=__palette_0> <label class="md-header__button md-icon" title="Switch to dark mode" for=__palette_1 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 8a4 4 0 0 0-4 4 4 4 0 0 0 4 4 4 4 0 0 0 4-4 4 4 0 0 0-4-4m0 10a6 6 0 0 1-6-6 6 6 0 0 1 6-6 6 6 0 0 1 6 6 6 6 0 0 1-6 6m8-9.31V4h-4.69L12 .69 8.69 4H4v4.69L.69 12 4 15.31V20h4.69L12 23.31 15.31 20H20v-4.69L23.31 12z"/></svg> </label> <input class=md-option data-md-color-media data-md-color-scheme=slate data-md-color-primary=indigo data-md-color-accent=indigo aria-label="Switch to light mode" type=radio name=__palette id=__palette_1> <label class="md-header__button md-icon" title="Switch to light mode" for=__palette_0 hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M12 18c-.89 0-1.74-.2-2.5-.55C11.56 16.5 13 14.42 13 12s-1.44-4.5-3.5-5.45C10.26 6.2 11.11 6 12 6a6 6 0 0 1 6 6 6 6 0 0 1-6 6m8-9.31V4h-4.69L12 .69 8.69 4H4v4.69L.69 12 4 15.31V20h4.69L12 23.31 15.31 20H20v-4.69L23.31 12z"/></svg> </label> </form> <script>var palette=__md_get("__palette");if(palette&&palette.color){if("(prefers-color-scheme)"===palette.color.media){var media=matc
|
||
|
|
and terminated by a control operator. The first word specifies the command to be executed, and is passed as argument
|
||
|
|
zero. The remaining words are passed as arguments to the invoked command.
|
||
|
|
</code></pre></div> <p>Sounds harder than it actually is. It is what you do daily. You enter simple commands with parameters, and the shell executes them.</p> <p>Every complex Bash operation can be split into simple commands:</p> <div class=highlight><pre><span></span><code>ls
|
||
|
|
ls > list.txt
|
||
|
|
ls -l
|
||
|
|
LC_ALL=C ls
|
||
|
|
</code></pre></div> <p>The last one might not be familiar. That one simply adds "<code>LC_ALL=C</code>" to the environment of the <code>ls</code> program. It doesn't affect your current shell. This also works while calling functions, unless Bash runs in POSIX® mode (in which case it affects your current shell).</p> <p>Every command has an exit code. It's a type of return status. The shell can catch it and act on it. Exit code range is from 0 to 255, where 0 means success, and the rest mean either something failed, or there is an issue to report back to the calling program.</p> <div class="admonition info"> <p class=admonition-title>info</p> <p>The simple command construct is the <strong>base</strong> for all higher constructs. Everything you execute, from pipelines to functions, finally ends up in (many) simple commands. That's why Bash only has one method to <a href=../grammar/parser_exec/ >expand and execute a simple command</a>.</p> </div> <h2 id=pipelines>Pipelines<a class=headerlink href=#pipelines title="Permanent link">¶</a></h2> <div class="admonition warning"> <p class=admonition-title>FIXME</p> <p>Missing an additional article about pipelines and pipelining</p> </div> <p><code>[time [-p]] [ ! ] command [ | command2 ... ]</code></p> <p><strong>Don't get confused</strong> about the name "pipeline." It's a grammatic name for a construct. Such a pipeline isn't necessarily a pair of commands where stdout/stdin is connected via a real pipe.</p> <p>Pipelines are one or more <a href=#simple-commands>simple commands</a> (separated by the <code>|</code> symbol connects their input and output), for example:</p> <div class=highlight><pre><span></span><code>ls /etc | wc -l
|
||
|
|
</code></pre></div> <p>will execute <code>ls</code> on <code>/etc</code> and <strong>pipe</strong> the output to <code>wc</code>, which will count the lines generated by the ls command. The result is the number of directory entries in /etc.</p> <p>The last command in the pipeline will set the exit code for the pipeline. This exit code can be "inverted" by prefixing an exclamation mark to the pipeline: An unsuccessful pipeline will exit "successful" and vice versa. In this example, the commands in the if stanza will be executed if the pattern "^root:" is <strong>not</strong> found in <code>/etc/passwd</code>:</p> <div class=highlight><pre><span></span><code>if ! grep '^root:' /etc/passwd; then
|
||
|
|
echo "No root user defined... eh?"
|
||
|
|
fi
|
||
|
|
</code></pre></div> <p>Yes, this is also a pipeline (although there is no pipe!), because the <strong>exclamation mark to invert the exit code</strong> can only be used in a pipeline. If <code>grep</code>'s exit code is 1 (FALSE) (the text was not found), the leading <code>!</code> will "invert" the exit code, and the shell sees (and acts on) exit code 0 (TRUE) and the <code>then</code> part of the <code>if</code> stanza is executed. One could say we checked for "<code>not grep "^root" /etc/passwd</code>".</p> <p>The <a href=../../commands/builtin/set/#attributes>set option pipefail</a> determines the behavior of how bash reports the exit code of a pipeline. If it's set, then the exit code (<code>$?</code>) is the last command that exits with non zero status, if none fail, it's zero. If it's not set, then <code>$?</code> always holds the exit code of the last command (as explained above).</p> <p>The shell option <code>lastpipe</code> will execute the last element in a pipeline construct in the current shell environment, i.e. not a subshell.</p> <p>There's also an array <code>PIPESTATUS[]</code> that is set after a foreground pipeline is executed. Each element of <code>PIPESTATUS[]</code> reports the exit code of the respective command in the pipeline. Note: (1) it's only for foreground pipe and (2) for higher level structure that is built up from a pipeline. Like list, <code>PIPESTATUS[]</code> holds the exit status of the last pipeline command executed.</p> <p>Another thing you can do with pipelines is log their execution time. Note that <strong><code>time</code> is not a command</strong>, it is part of the pipeline syntax:</p> <div class=highlight><pre><span></span><code># time updatedb
|
||
|
|
real 3m21.288s
|
||
|
|
user 0m3.114s
|
||
|
|
sys 0m4.744s
|
||
|
|
</code></pre></div> <h2 id=lists>Lists<a class=headerlink href=#lists title="Permanent link">¶</a></h2> <div class="admonition warning"> <p class=admonition-title>FIXME</p> <p>Missing an additional article about list operators</p> </div> <p>A list is a sequence of one or more <a href=#pipelines>pipelines</a> separated by one of the operators <code>;</code>, <code>&</code>, <code>&&</code>, or <code>││</code>, and optionally terminated by one of <code>;</code>, <code>&</code>, or <code><newline></code>.</p> <p>=> It's a group of <strong>pipelines</strong> separated or terminated by <strong>tokens</strong> that all have <strong>different meanings</strong> for Bash.</p> <p>Your whole Bash script technically is one big single list!</p> <table> <thead> <tr> <th>Operator</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td><code><PIPELINE1> <newline> <PIPELINE2></code></td> <td>Newlines completely separate pipelines. The next pipeline is executed without any checks. (You enter a command and press <code><RETURN></code>!)</td> </tr> <tr> <td><code><PIPELINE1> ; <PIPELINE2></code></td> <td>The semicolon does what <code><newline></code> does: It separates the pipelines</td> </tr> <tr> <td><code><PIPELINE> & <PIPELINE></code></td> <td>The pipeline in front of the <code>&</code> is executed <strong>asynchronously</strong> ("in the background"). If a pipeline follows this, it is executed immediately after the async pipeline starts</td> </tr> <tr> <td><code><PIPELINE1> && <PIPELINE2></code></td> <td><code><PIPELINE1></code> is executed and <strong>only</strong> if its exit code was 0 (TRUE), then <code><PIPELINE2></code> is executed (AND-List)</td> </tr> <tr> <td><code><PIPELINE1>||<PIPELINE2></code></td> <td><code><PIPELINE1></code> is executed and <strong>only</strong> if its exit code was <strong>not</strong> 0 (FALSE), then <code><PIPELINE2></code> is executed (OR-List)</td> </tr> </tbody> </table> <p><strong>Note:</strong> POSIX calls this construct a "compound lists".</p> <h2 id=compound-commands>Compound Commands<a class=headerlink href=#compound-commands title="Permanent link">¶</a></h2> <p>See also the <a href=../ccmd/intro/ >list of compound commands</a>.</p> <p>There are two forms of compound commands:</p> <ul> <li>form a new syntax element using a list as a "body"</li> <li>completly independant syntax elements</li> </ul> <p>Essentially, everything else that's not described in this article. Compound commands have the following characteristics:</p> <ul> <li>they <strong>begin</strong> and <strong>end</strong> with a specific keyword or operator (e.g. <code>for ... done</code>)</li> <li>they can be redirected as a whole</li> </ul> <p>See the following table for a short overview (no details - just an overview):</p> <table> <thead> <tr> <th>Compound command syntax</th> <th>Description</th> </tr> </thead> <tbody> <tr> <td><code>( <LIST> )</code></td> <td>Execute <code><LIST></code> in an extra subshell => <a href=../ccmd/grouping_subshell/ >article</a></td> </tr> <tr> <td><code>{ <LIST> ; }</code></td> <td>Execute <code><LIST></code> as separate group (but not in a subshell) => <a href=../ccmd/grouping_plain/ >article</a></td> </tr> <tr> <td><code>(( <EXPRESSION> ))</code></td> <td>Evaluate the arithmetic expression <code><EXPRESSION></code> => <a href=../ccmd/arithmetic_eval/ >article</a></td> </tr> <tr> <td><code>[[ <EXPRESSION> ]]</code></td> <td>Evaluate the conditional expression <code><EXPRESSION></code> (aka "the new test command") => <a href=../ccmd/conditional_expression/ >article</a></td> </tr> <tr> <td><code>for <NAME> in <WORDS> ; do <LIST> ; done</code></td> <td>Executes <code><LIST></code> while setting the variable <code><NAME></code> to one of <code><WORDS></code> on every iteration (classic for-loop) => <a href=../ccmd/classic_for/ >article</a></td> </tr>
|
||
|
|
</code></pre></div> <p>As above, a function definition can have any <a href=#compound_commands>compound command</a> as a body. Structures like</p> <div class=highlight><pre><span></span><code>countme() for ((x=1;x<=9;x++)); do echo $x; done
|
||
|
|
</code></pre></div> <p>are unusual, but perfectly valid, since the for loop construct is a compound command!</p> <p>If <strong>redirection</strong> is specified, the redirection is not performed when the function is defined. It is performed when the function runs:</p> <div class=highlight><pre><span></span><code># this will NOT perform the redirection (at definition time)
|
||
|
|
f() { echo ok ; } > file
|
||
|
|
|
||
|
|
# NOW the redirection will be performed (during EXECUTION of the function)
|
||
|
|
f
|
||
|
|
</code></pre></div> <p>Bash allows three equivalent forms of the function definition:</p> <div class=highlight><pre><span></span><code>NAME () <COMPOUND_COMMAND> <REDIRECTIONS>
|
||
|
|
function NAME () <COMPOUND_COMMAND> <REDIRECTIONS>
|
||
|
|
function NAME <COMPOUND_COMMAND> <REDIRECTIONS>
|
||
|
|
</code></pre></div> <p>The space between <code>NAME</code> and <code>()</code> is optional, usually you see it without the space.</p> <p>I suggest using the first form. It's specified in POSIX and all Bourne-like shells seem to support it.</p> <p><u><strong>Note:</strong></u> Before version <code>2.05-alpha1</code>, Bash only recognized the definition using curly braces (<code>name() { ... }</code>), other shells allow the definition using <strong>any</strong> command (not just the compound command set).</p> <p>To execute a function like a regular shell script you put it together like this:</p> <div class=highlight><pre><span></span><code>#!/bin/bash
|
||
|
|
# Add shebang
|
||
|
|
|
||
|
|
mycmd()
|
||
|
|
{
|
||
|
|
# this $1 belongs to the function!
|
||
|
|
find / -iname "$1"
|
||
|
|
}
|
||
|
|
|
||
|
|
# this $1 belongs the script itself!
|
||
|
|
mycmd "$1" # Execute command immediately after defining function
|
||
|
|
|
||
|
|
exit 0
|
||
|
|
</code></pre></div> <p><strong>Just informational(1):</strong></p> <p>Internally, for forking, Bash stores function definitions in environment variables. Variables with the content "<em>() ....</em>".</p> <p>Something similar to the following works without "officially" declaring a function:</p> <div class=highlight><pre><span></span><code>$ export testfn="() { echo test; }"
|
||
|
|
$ bash -c testfn
|
||
|
|
test
|
||
|
|
$
|
||
|
|
</code></pre></div> <p><strong>Just informational(2):</strong></p> <p>It is possible to create function names containing slashes:</p> <div class=highlight><pre><span></span><code>/bin/ls() {
|
||
|
|
echo LS FAKE
|
||
|
|
}
|
||
|
|
</code></pre></div> <p>The elements of this name aren't subject to a path search.</p> <p>Weird function names should not be used. Quote from the maintainer:</p> <ul> <li> <ul> <li>It was a mistake to allow such characters in function names (<code>unset</code> doesn't work to unset them without forcing <code>-f</code>, for instance). We're stuck with them for backwards compatibility, but I don't have to encourage their use. *</li> </ul> </li> </ul> <h2 id=grammar-summary>Grammar summary<a class=headerlink href=#grammar-summary title="Permanent link">¶</a></h2> <ul> <li>a <a href=#simple_commands>simple command</a> is just a command and its arguments</li> <li>a <a href=#pipelines>pipeline</a> is one or more <a href=#simple_commands>simple command</a> probably connected in a pipe</li> <li>a <a href=#lists>list</a> is one or more <a href=#pipelines>pipelines</a> connected by special operators</li> <li>a <a href=#compound_commands>compound command</a> is a <a href=#lists>list</a> or a special command that forms a new meta-command</li> <li>a <a href=#shell_function_definitions>function definition</a> makes a <a href=#compound_commands>compound command</a> available under a new name, and a separate environment</li> </ul> <h2 id=examples-for-classification>Examples for classification<a class=headerlink href=#examples-for-classification title="Permanent link">¶</a></h2> <div class="admonition warning"> <p class=admonition-title>FIXME</p> <p>more...</p> </div> <hr> <p><u>A (very) simple command</u></p> <div class=highlight><pre><span></span><code>echo "Hello world..."
|
||
|
|
</code></pre></div> <p><u>All of the following are simple commands</u></p> <div class=highlight><pre><span></span><code>x=5
|
||
|
|
|
||
|
|
>tmpfile
|
||
|
|
|
||
|
|
{x}<"$x" _=${x=<(echo moo)} <&0$(cat <&"$x" >&2)
|
||
|
|
</code></pre></div> <hr> <p><u>A common compound command</u></p> <div class=highlight><pre><span></span><code>if [ -d /data/mp3 ]; then
|
||
|
|
cp mymusic.mp3 /data/mp3
|
||
|
|
fi
|
||
|
|
</code></pre></div> <ul> <li>the <a href=#compound_commands>compound command</a> for the <code>if</code> clause</li> <li>the <a href=#lists>list</a> that <code>if</code> <strong>checks</strong> actually contains the <a href=#simple_commands>simple command</a> <code>[ -d /data/mp3 ]</code></li> <li>the <a href=#lists>list</a> that <code>if</code> <strong>executes</strong> contains a simple command (<code>cp mymusic.mp3 /data/mp3</code>)</li> </ul> <p>Let's invert test command exit code, only one thing changes:</p> <div class=highlight><pre><span></span><code>if ! [ -d /data/mp3 ]; then
|
||
|
|
cp mymusic.mp3 /data/mp3
|
||
|
|
fi
|
||
|
|
</code></pre></div> <ul> <li>the <a href=#lists>list</a> that <code>if</code> <strong>checks</strong> contains a <a href=#pipelines>pipeline</a> now (because of the <code>!</code>)</li> </ul> <h2 id=see-also>See also<a class=headerlink href=#see-also title="Permanent link">¶</a></h2> <ul> <li>Internal: <a href=../ccmd/intro/ >List of compound commands</a></li> <li>Internal: <a href=../grammar/parser_exec/ >Parsing and execution of simple commands</a></li> <li>Internal: <a href=../quoting/ >Quoting and escaping</a></li> <li>Internal: <a href=../expansion/intro/ >Introduction to expansions and substitutions</a></li> <li>Internal: <a href=../words/ >Some words about words...</a></li> </ul> <aside class=md-source-file> <span class=md-source-file__fact> <span class=md-icon title="Last update"> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1zM12.5 7v5.2l4 2.4-1 1L11 13V7zM11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">November 13, 2024</span> </span> <span class=md-source-file__fact> <span class=md-icon title=Created> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M14.47 15.08 11 13V7h1.5v5.25l3.08 1.83c-.41.28-.79.62-1.11 1m-1.39 4.84c-.36.05-.71.08-1.08.08-4.42 0-8-3.58-8-8s3.58-8 8-8 8 3.58 8 8c0 .37-.03.72-.08 1.08.69.1 1.33.32 1.92.64.1-.56.16-1.13.16-1.72 0-5.5-4.5-10-10-10S2 6.5 2 12s4.47 10 10 10c.59 0 1.16-.06 1.72-.16-.32-.59-.54-1.23-.64-1.92M18 15v3h-3v2h3v3h2v-3h3v-2h-3v-3z"/></svg> </span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">November 13, 2024</span> </span> </aside> <h2 id=__comments>Comments</h2> <script src=https://giscus.app/client.js data-repo=flokoe/bash-hackers-wiki data-repo-id=R_kgDOJ3Nr6Q data-category="Giscus Page Comments" data-category-id=DIC_kwDOJ3Nr6c4CXq9t data-mapping=pathname data-strict=1 data-reactions-enabled=1 data-emit-metadata=0 data-input-position=top data-theme=preferred_color_scheme data-lang=en data-loading=lazy crossorigin=anonymous async>
|
||
|
|
</script> <script>
|
||
|
|
var giscus = document.querySelector("script[src*=giscus]")
|
||
|
|
|
||
|
|
/* Set palette on initial load */
|
||
|
|
var palette = __md_get("__palette")
|
||
|
|
if (palette && typeof palette.color === "object") {
|
||
|
|
var theme = palette.color.scheme === "slate" ? "dark" : "light"
|
||
|
|
giscus.setAttribute("data-theme", theme)
|
||
|
|
}
|
||
|
|
|
||
|
|
/* Register event handlers after documented loaded */
|
||
|
|
document.addEventListener("DOMContentLoaded", function() {
|
||
|
|
var ref = document.querySelector("[data-md-component=palette]")
|
||
|
|
ref.addEventListener("change", function() {
|
||
|
|
var palette = __md_get("__palette")
|
||
|
|
if (palette && typeof palette.color === "object") {
|
||
|
|
var theme = palette.color.scheme === "slate" ? "dark" : "light"
|
||
|
|
|
||
|
|
/* Instruct Giscus to change theme */
|
||
|
|
var frame = document.querySelector(".giscus-frame")
|
||
|
|
frame.contentWindow.postMessage(
|
||
|
|
{ giscus: { setConfig: { theme } } },
|
||
|
|
"https://giscus.app"
|
||
|
|
)
|
||
|
|
}
|
||
|
|
})
|
||
|
|
})
|
||
|
|
</script> </article> </div> <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script> </div> <button type=button class="md-top md-icon" data-md-component=top hidden> <svg xmlns=http://www.w3.org/2000/svg viewbox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg> Back to top </button> </main> <footer class=md-footer> <div class="md-footer-meta md-typeset"> <div class="md-footer-meta__inner md-grid"> <div class=md-copyright> Made with <a href=https://squidfunk.github.io/mkdocs-material/ target=_blank rel=noopener> Material for MkDocs </a> </div> </div> </div> </footer> </div> <div class=md-dialog data-md-component=dialog> <div class="md-dialog__inner md-typeset"></div> </div> <script id=__config type=application/json>{"base": "../..", "features": ["navigation.instant", "navigation.tracking", "navigation.tabs", "navigation.sections", "navigation.top", "content.action.view", "content.action.edit", "search.suggest", "search.highlight", "content.code.copy"], "search": "../../assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}}</script> <script src=../../assets/javascripts/bundle.83f73b43.min.js></script> </body> </html>
|