Skip to content

Commit 0fffa8b

Browse files
committed
Fix formatting in cmdline examples
1 parent 62e47f3 commit 0fffa8b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/main/resources/docs/Command_Line_Scripting

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,12 +35,12 @@ throwing a stack trace or something. This is not a bug per-se, you must simply n
3535

3636
To use the cmdline tools, there are three methods. First, the cmdline interpreter can be accessed by simply running
3737
<code>mscript</code>. This simply runs the command line interpreter, which is in fact the engine for all the other
38-
methods. The second method is to use <code>mscript <filename></code>. This executes the file, assuming it is a valid
38+
methods. The second method is to use <code>mscript &gt;filename&lt;</code>. This executes the file, assuming it is a valid
3939
pure mscript file.
4040

4141
Finally, you may execute a MethodScript file on unix systems by executing it directly. To do so, be sure to put
4242
<code>#!/usr/bin/env /usr/local/bin/mscript</code> at the top of your file, then set the file's execution bit,
43-
using <code>chmod +x <filename></code>. Then, you may simply run <code>./script.ms</code> (assuming the filename is
43+
using <code>chmod +x &gt;filename&lt;</code>. Then, you may simply run <code>./script.ms</code> (assuming the filename is
4444
script.ms). Using the cmdline tool "new" you can create a blank file with the file set up correctly.
4545
[[CommandLineTools#Tool listing|See this page]]
4646

0 commit comments

Comments
 (0)