Rune
From Erights
(→Setting up rune) |
(→Setting up rune) |
||
| (9 intermediate revisions not shown) | |||
| Line 13: | Line 13: | ||
As an alternative, rune can be started using the java executable: | As an alternative, rune can be started using the java executable: | ||
| - | <code> | + | <code>$ java -jar e.jar --rune</code> |
| - | java -jar e.jar --rune | + | |
| - | </code> | + | |
== Running an E script from rune == | == Running an E script from rune == | ||
| - | There are | + | There are several ways to start an E script using rune. |
| - | + | ||
| - | + | === Calling the "rune" script explicitly === | |
| - | + | Given that the "rune" script is on your PATH, you can give the name of the .e script as a command line argument to rune: | |
| - | <code>? rune(["example.e"])</code> | + | <code>$ rune [options...] example.e [args...]</code> |
| + | |||
| + | The additional args after <code>example.e</code> are available from within <code>example.e</code> as the value of the expression | ||
| + | |||
| + | <code>interp.getArgs()</code> | ||
| + | |||
| + | For more information on the options, do | ||
| + | |||
| + | <code>$ rune --help</code> | ||
| + | |||
| + | === Calling the "rune" shell script implicitly === | ||
| + | |||
| + | On the unix/linux/mac/cygwin platforms, you can place <code>#!/usr/bin/env rune</code> on the first line of example.e, make example.e executable, and use it directly as a command: | ||
| + | |||
| + | <code>$ example.e [args...]</code> | ||
| + | |||
| + | On cygwin, text files beginning with a "#!" are automatically considered executable. | ||
| + | |||
| + | === Calling the "rune" function from within a running E system === | ||
| + | |||
| + | You can start the script directly from the E command prompt, which can save some time because the running Java VM is used: | ||
| + | |||
| + | <code>? rune(["example.e"])</code> | ||
| + | |||
| + | === Launching from the desktop === | ||
| + | |||
| + | Currently on Windows only, you can double click on the shortcut icon for <code>example.e</code> in the file explorer (desktop). | ||
== Command history == | == Command history == | ||
The interactive E interpreter does not provide command history. Under windows, the shell has its own command history, which can be used by pressing the up and down arrow keys. | The interactive E interpreter does not provide command history. Under windows, the shell has its own command history, which can be used by pressing the up and down arrow keys. | ||
If your system does not provide command history, you can try [http://freshmeat.net/projects/rlwrap/ rlwrap]. | If your system does not provide command history, you can try [http://freshmeat.net/projects/rlwrap/ rlwrap]. | ||
Latest revision as of 22:52, 15 March 2007
Rune is the interactive command line interpreter for E code.
Contents |
Setting up rune
Windows: Copy the file rune-bat-template.txt to rune.bat and edit the settings in the file.
Hint: If you plan on using rune a lot, you should try Console, a Windows console window enhancement
unix/linux/mac/cygwin: Copy rune-template.txt to rune and edit it.
Add execute rights to the file by entering chmod a+x rune.
You should now be able to execute rune and get an interactive shell.
As an alternative, rune can be started using the java executable:
$ java -jar e.jar --rune
Running an E script from rune
There are several ways to start an E script using rune.
Calling the "rune" script explicitly
Given that the "rune" script is on your PATH, you can give the name of the .e script as a command line argument to rune:
$ rune [options...] example.e [args...]
The additional args after example.e are available from within example.e as the value of the expression
interp.getArgs()
For more information on the options, do
$ rune --help
Calling the "rune" shell script implicitly
On the unix/linux/mac/cygwin platforms, you can place #!/usr/bin/env rune on the first line of example.e, make example.e executable, and use it directly as a command:
$ example.e [args...]
On cygwin, text files beginning with a "#!" are automatically considered executable.
Calling the "rune" function from within a running E system
You can start the script directly from the E command prompt, which can save some time because the running Java VM is used:
? rune(["example.e"])
Launching from the desktop
Currently on Windows only, you can double click on the shortcut icon for example.e in the file explorer (desktop).
Command history
The interactive E interpreter does not provide command history. Under windows, the shell has its own command history, which can be used by pressing the up and down arrow keys. If your system does not provide command history, you can try rlwrap.
