ldomterm application is the preferred away of
using DomTerm, so plain
normally installed as an alias for it.
If you run
ldomterm with no arguments, you get a
fairly nice terminal emulator, just as if you’d start
ldomterm program is primarily a server
for WebSockets and http. When it receives a connection,
it runs a specified command, by default a shell.
--port is specified,
ldomterm will automatically
start a browser session (the “front-end”) that connects
to the server. The default is currently
as if you specified
--browser (if the
electron is not found).
command specifies one of a set of commands used to control
domterm, as described in the following sections.
command is specified, it creates a new session,
by default using a shell such as
The following options control which front-end (usually a browser), if any, is started.
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 new a new terminal window,
as specified a window specifier.
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 replaced 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).
This is no longer supported.
This is similar to the
--chrome option, but using
bare Firefox browser window, with
a custom menubar, and custom context menu (what you get by right-clicking).
This is based on XUL,
which is being phased out.
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.
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.