jdomterm script is no longer recommended as a general terminal-emulator.
It can be useful when using Java as it does not require native code.
By default it runs a shell (
bash), but there are a number of options.
The frontend argument specifies the front-end or user interface application - i.e. some kind of browser. The backend-arguments specify which command is run and how it is run.
The frontend is one of the following:
Similar to the
The UI (written in Java using the JavaFX toolkit) is minimal, but right-clicking will bring up a popup menu. This supports copy and paste, as well as switching the input mode between line, character, or auto mode.
There are some glitches, and since JavaFX is not being actively developed, this port is not a priority.
Start a WebSocket server, listening on the specified portnum.
(A portnum of 0 lets the system choose an available port,
which is printed out. The default for
No front-end is started automatically.
Instead, you load
repl-client.html in your preferred web browser,
and it connects to the server.
If the server is listening on port portnum (rather than port 8025),
The backend-arguments are one of:
-e] [command arg...]
You can specify some other command and arg in
place of the default
This is the default on Unix-like systems (MacOs, GNU/Linux, BSD). It runs command under a PTY. Communication is by default character-by-character, but can also be line-based.
The input/output of the command is connected to DomTerm using
pipes. Data communication is normally on a line-by-line basis.
(It is also possible to send single keystroke message.)
The implementations uses a Java
This should work on Windows, though it has not yet been tested.
This runs the
main method of a specified Java class,
but with the standard streams (input, output, and error)
re-bound to a DomTerm window.
CLASSPATH=my-application.jar domterm --class my.ClassName arg...