You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: manual/master/index.html
+17-9Lines changed: 17 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -9779,8 +9779,8 @@ <h2>input.conf syntax</h2>
9779
9779
<p><tt class="docutils literal"><section></tt> (braced with <tt class="docutils literal">{</tt> and <tt class="docutils literal">}</tt>) is the input section for this
9780
9780
command.</p>
9781
9781
<p><tt class="docutils literal"><command></tt> is the command itself. It consists of the command name and
9782
-
multiple (or none) commands, all separated by whitespace. String arguments
9783
-
need to be quotedwith <tt class="docutils literal">"</tt>. Details see <tt class="docutils literal">Flat command syntax</tt>.</p>
9782
+
multiple (or none) arguments, all separated by whitespace. String arguments
9783
+
should be quoted, typically with <tt class="docutils literal">"</tt>. See <tt class="docutils literal">Flat command syntax</tt>.</p>
9784
9784
<p>You can bind multiple commands to one key. For example:</p>
<p><tt class="docutils literal">command_name</tt> is an unquoted string with the command name itself. See
9866
9866
<a class="reference internal" href="#list-of-input-commands">List of Input Commands</a> for a list.</p>
9867
-
<p>Arguments are separated by whitespace. This applies even to string arguments.
9868
-
For this reason, string arguments should be quoted with <tt class="docutils literal">"</tt>. If a string
9869
-
argument contains spaces or certain special characters, quoting and possibly
9870
-
escaping is mandatory, or the command cannot be parsed correctly.</p>
9871
-
<p>Inside quotes, C-style escaping can be used. JSON escapes according to RFC 8259,
9872
-
minus surrogate pair escapes, should be a safe subset that can be used.</p>
9867
+
<p>Arguments are separated by whitespaces even if the command expects only one
9868
+
argument. Arguments with whitespaces or other special characters must be quoted,
9869
+
or the command cannot be parsed correctly.</p>
9870
+
<p>Double quoted arguments start and end with <tt class="docutils literal">"</tt>. Custom quotes start with <tt class="docutils literal">!</tt>
9871
+
(exclamation mark) followed by any ASCII character, and end in the same pair in
9872
+
reverse order, e.g. <tt class="docutils literal">!'foo'!</tt> or <tt class="docutils literal"><span class="pre">!-bar-!</span></tt>. The final pair sequence is not
9873
+
allowed inside the string - in these examples <tt class="docutils literal">'!</tt> and <tt class="docutils literal"><span class="pre">-!</span></tt> respectively.</p>
9874
+
<p>Custom quotes take their content literally, while inside double quotes
9875
+
JSON/C-style escaping can be used. JSON escapes according to RFC 8259, minus
9876
+
surrogate pair escapes, should be a safe subset that can be used.</p>
9877
+
<p>Note that argument parsing and property expansion happen at different stages.
9878
+
First, arguments are determined as described above, and then, where applicable,
9879
+
properties are expanded - regardless of argument quoting. However, expansion
9880
+
can still be prevented with <tt class="docutils literal">$></tt>. See <a class="reference internal" href="#property-expansion">Property Expansion</a>.</p>
0 commit comments