Per Bothner

Is the problem also present on Chrome? What about Firefox? (You probably don't want to use a regular browser for your normal terminal, but `--chrome-app` is definitely usable, as is...

I agree this would be nice, and I would support it. However, there are some other "big-ticket" items on the roadmap that I'm focusing on before native-Windows support. If someone...

I added some instructions for building and using [electron-nodepty](https://domterm.org/electron-nodepty.html), after verifying that it works on plain (non-WSL) Windows (after fixing a couple of issues).

_"Looks like the build requires installing Visual Studio."_ I assume that is because of the node-pty package. I agree pre-built binaries would be very nice, but that's a lot of...

I checked in a fix/work-around for this: When the WebSocket connection is closed without user action, the JavaScript will create a new connection. Preliminary testing seems to work with both...

Some of these could be font issues: I.e. not all of the characters have the same width. It might be useful if you could try standalone domterm (i.e not atom-domterm):...

_It displays it correctly, but in a fresh prompt, I can press the delete key and delete parts of the prompt. E.g. in the Fish, I can delete 2 chars_...

I have little-to-no powershell experience. If you could tell me precise steps to reproduce the problems (included expected behaviour vs observed behavior) I can try to reproduce (and hopefully debug)...

I think you must be running an old version of domterm - those line numbers don't make sense. (Also, `pwsh` isn't in the PATH - but `powershell.exe` works.)

Just as a sanity check: `echo $DOMTERM` yields a string starting with `version=2.1.0`? Also, the `domterm status` command prints out lots of useful information, I would expect it to start...