Skip to content

Commit f48947c

Browse files
committed
add note about escaping semicolons
1 parent bb50db8 commit f48947c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

documentation/usersguide/objectdefinitions.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ for otherwise tedious configuration tasks.{{ site.end }}
2929
<ol>
3030
<li>Lines that start with a '#' character are taken to be comments and are not processed</li>
3131
<li>Directive names are case-sensitive</li>
32-
<li>Characters that appear after a semicolon (;) in configuration lines are treated as comments and are not processed</li>
32+
<li>Characters that appear after a (unescaped) semicolon (;) in configuration lines are treated as comments and are not processed</li>
3333
</ol>
3434
{{ site.end }}
3535

@@ -1857,7 +1857,7 @@ Also, if you want to pass a dollar sign ($) on the command line, you have to esc
18571857
</p>
18581858
<p><strong>NOTE</strong>: You may not include a <b>semicolon</b> (;) in the <i>command_line</i> directive, because everything after it will be ignored as a config file comment.
18591859

1860-
You can work around this limitation by setting one of the <a href="macrolist.html#user"><b>$USER$</b></a> macros in your <a
1860+
You can work around this limitation by escaping the semicolon with a backslash or by setting one of the <a href="macrolist.html#user"><b>$USER$</b></a> macros in your <a
18611861
href="configmain.html#resource_file">resource file</a> to a semicolon and then referencing the appropriate $USER$ macro in the <i>command_line</i> directive in place of the semicolon.
18621862
</p>
18631863
<p>

0 commit comments

Comments
 (0)