Per Bothner

issues specific to macOS

1

Here are [simplified and tested build instructions](http://domterm.org/Downloading-and-building.html#macos-build-simple) for macOS (tested on Monterrey with HomeBrew and Qt6). Some issues specific to running DomTerm on macOS: * Window buttons ("traffic lights") when...

RoadMap

12

This roadmap implies no commitment. Priorities may change depending on unexpected difficulties or insights, user requests, or whim. ## Short-term These items are being worked on: * Make custom titlebar...

problems on WebKit/WebKitGtk

1

WebKit-based browsers (at least WebKitGtk) have some extra issues. This affects Gnome Web (Epiphany), Wry, WebView. * Neither `beforeunload` or `pagehide` event is fired on window close, which means we...

WebSockets connection closed after sleep on Chrome on Mac

1

When sleeping on MacOS, using Google Chromium (Chrome or Electron or Qt) the WebSocket connection is closed with a code of 1006 (Abnormal closure). This does not happen when using...

new qtdomterm frontend could use more porting and testing

2

I wrote a new self-contained terminal emulator using DomTerm and qtwebengine. At this point it's pretty nice and I'm going to try using it as my primary terminal emulator. However,...

output should start at screen top if one screen

9

When displaying a single line (or more generally less than a screenfull) and not using `--quit-if-one-screen` there is a "random" number of blank lines before the output, which is confusing....

Web-based (can run using Electron or in a browser); solid xterm compatibility; embedded html/graphics/rich text; nice features for REPLs. Home page: https://domterm.org/ A good summary/introduction: https://opensource.com/article/18/1/introduction-domterm-terminal-emulator

can't find comprensive documentation of nu invocation and command-line switches

1

### Related problem Is there a place where the `nu` command itself is documented in detail, including all the command-line switches? Something like the output of `nu --help` but in...

The claim "supports all UNIX terminals" should probably be changed to something like "supports most modern terminal emulators that use xterm-style escape sequences". I don't see anything in the code...

I have a usable prototype using the HTML drag-and-drop. It supports (with some glitches): * Drag from one window and drop to another. * Drag from one window and drop...