WinCommand is an application that can run a console (like CLisp or cmd) inside a window. For example you can run CLisp inside a window so you can work more confortable.
The program can be configured for any (I hope) console application, like others implementations of lisp (Corman Lisp, GCL,...).
You can save the history of command typed inside the console and save the whole text of the console.
Enjoy it, and send comments!!!
$cls: clear the console.
Global command execution:
If you put some command inside this textbox and press Ctrl+Enter, or click in the green arrow or click in Tools - Exec Global Cmd. Useful when you want to execute the same command continuously, like a function defintion or, in my situation, repetitive commands like (load "foo") when you are working foo.clj
WinCommand.ini is the file that let you configure WinCommand.
This is the format of each application line definition:
App Name | App executable path | App parameters | internal command to leave the repl environment and exit the App
You can use [expand-resource("$WCMD-HOME\usr\lib\","*.jar",";")] if you want to expand this expression to the path of all the files (Ex. .jar) that are in the specified path (Ex. $WCMD-HOME\usr\lib\) using the separator (Ex. ;) between them. Very useful to add files to the classpath.
The next area that you will find is the environment area.
Here you can add environment variables that will be set to the Application environment only. For example, BOX-HOME is set with the value $WCMD-HOME that is an internal variable defined in runtime that contains WinCommand execution path.
You can change JAVA_HOME=C:\Sun\SDK\jdk to your J2SE JDK default location.
If you want to use some of this variables in you Application definition you must put the "main.system.command-prefix" before the variable name.
Finally you will find the setup area that let you change the global behaviour of WinCommand.[setup]