domterm command is the preferred away of using DomTerm.
If you run
domterm with no arguments, it creates a new terminal
emulator window, just as if you’d start
You can specify options to specify what kind of window is
created (for example a new tab or a web browser window).
You can also specify a
command to perform other actions
besides creating a new terminal emulator.
command specifies one of a set of commands used to control
domterm, as described in the following sections.
command is not specified, the default command is
which creates a new session using a default shell such as
Creating a new session is done with the
This creates a new process running the
with the specified command-line arguments.
You can leave out the
new if the
contains a “
/” (slash). For example:
$ domterm /bin/csh -v
executable is not specified, the default shell
bin/bash) is used.
executable runs a new terminal window,
as specified a window specifier.
The following options control which front-end (usually a browser), if any, is started.
window-specifier option with certain commands,
attach. For example:
domterm --electron new domterm --below attach '#4' domterm --browser=firefox /bin/sh
program as a browser to run DomTerm in.
program is not specified,
creates a new window or tab in your preferred desktop browser.
program is specified, instead creates a window
in the specified browser, where
program is the name
of a browser program that takes a single URL argument.
program can be a multi-word template,
%U is replaced by a URL generated by
program enables some special tricks to search for those browsers.
google-chrome has the same effect.)
Use a front-end based on Electron. This is currently the nicest (and default) front-end.
This uses the Google Chrome browser,
started using the
so you get a fresh chrome-less window (with no menubar or toolbar).
This works well and the performance is good. This method provides no menubar or context-menu customization (so far).
Experimental (not all functionality is working).
Either option (they do the same thing)
qtdomterm with the
after starting up a websockets server.
If there is a current DomTerm window, split it in two, and create a new window to the left/right/above/below the old one.
Equivalent to either
on the current window’s width/height ratio.
Succeeds (exits with code 0) if the current terminal is DomTerm; fails (exits with code -1) otherwise.
This test does not depend on environment variables,
but instead sends a special request code, and checks the response.
This test works over an
(The test does require that either
DOMTERM be non-empty,
TERM be either empty or contain the string
otherwise it does not try to the request code.)
Use this to embed HTML content info the DomTerm page. If there are no arguments, read from standard input. Either of the following work:
echo 'E = mc<sup>2</sup>' | domterm html domterm html 'E = mc<sup>2</sup>'
E = mc2.
Create a new window displaying an existing session. The same session (process) may be displayed in multiple windows. (Work-in-progress.)
List information about running sessions.
When a domterm backend (server) is created, it normally turns itself into a a daemon. This option prevents “deamonizing” - which is helpful for debugging.
Start a server, listening on the specified
portnum of 0 lets the system choose an available port,
which is printed out. No front-end is started.
Only allow a single connect before shutting down.
This option is the default unless
--port is specified.
There are other
ldomterm options which useful
if you want to run DomTerm as a server.