See home page and this introductory article for more information.
Better vtnnn/xterm compatibility, as demonstrated by the vttest testsuite.
You can embed graphics, html text, and more in the output.
For example help text can be rich html text.
(domterm help by default emits rich text on DomTerm.)
Output folding (show/hide buttons).
Compiler and other error messages (of the form filename:line) are clickable. (Needs hooking in Theia.)
Move cursor in bash or other readline-based program with mouse. (Requires setting of special escape sequences in prompt.)
Builtin LISP-style pretty-printer with re-flow on window re-size.
Optional line-editing for program that don't have readline or similar. (Potentially could use Monaco key-bindings and edit actions.)
Optional built-in pager (like less).
A styling problem with the scroll-bar - it's almost invisible.
Should set DOMTERM environment variable. That requires domterm-version.js.
Automatic input mode (swiching between characater-at-a-time and
line-editing mode based on therm state) is not implemented.
That requires a cll to tcgetattr.
Handling of clicked links is not implemented. File links with line numbers should open a file in the editor; other links should by default open the link in a browser. (The domterm program supports a flexible if complex way to specify how such links are handled.)
Flow-control (output rate limitation) is not implemented. This is related to the paging/pause support.
The domterm program (see build instructions)
provides a number of useful features beyond just starting a terminal emulator.
For example the domterm imgcat sub-command lets you "print"
an image to the current terminal.
This and similar "client" sub-commands work under Theia's domterm embedding.
The domterm program has useful "server-side" features that could be
re-implemented in typescript/node, but it may make more sense
to use the domterm command itself from Theia. That gives us
a lot of features already implemented: Session management (attach/save/detach);
handling of clicked links; flow control; watching and parsing the
settings.ini preferences file (a more friendly syntax that JSON).
Communication between the DomTerm JavaScript code and the domterm
program usea a WebSocket, so it shouldn't be to hard to provide
a mode for the Theia terminal to use the domterm program.
(Using external domterm, if available, should be a user preference.)