DomTerm

Stack traces are very valuable. Sometimes it can even help to attach them to some object creation, when you later wonder why/how/where this object was created. E.g. in TensorFlow, every single Tensor had a traceback attached to it, so when there was any error later on, it would show you where it was created. This is maybe less needed now with eager mode, but you might have other similar situations. One problem with stack traces is maybe that they can be too verbose. E.g. if you print them for any warning you print to log (or stdout). Sometimes they will be extremely helpful for debugging some problem, but in many cases, you maybe don't need them (you know why you get the warning and/or you don't care about it). You could also add more information to the stack trace such as local variables. That can be even more helpful for debugging then,

Please try DomTerm (https://domterm.org). The 2.9.4 AppImage (https://github.com/PerBothner/DomTerm/releases/tag/2.9.4) should have the needed support for grapheme clusters and hopefully work on reasonably up-to-date Linux systems. Of course there are more recent fixes and improvements if you don't mind building from source.

DomTerm has nice remote-terminal solution: https://domterm.org/Remoting-over-ssh.html . Compared to mosh is supports a much more complete xterm-like terminal, full scrollback, runs on Windows (using WSL), does not require superuser/admin access (runs on top of plain ssh), has an integrated tmux-style multiplier, and is actively developed. Like mosh it has predictive echo, and detach/attach. It also has an optional local-input-edit mode (used by default if the remote terminal is in icanon mode). An easily-installable AppImage is available (https://github.com/PerBothner/DomTerm/releases). Feedback welcome.

Seems to work fine with DomTerm (https://domterm.org): In a DomTerm terminal, I typed the command at the start of the SYNOPSIS, replacing the --terminal option with --terminal domterm, and got a really nice plot. (The simplest way to try out DomTerm is using DomTerm-X.Y.Z.AppImage from https://github.com/PerBothner/DomTerm/releases.)

Could you create an issue on the DomTerm git site (https://github.com/PerBothner/DomTerm)? There are two separate issues, I think: The protocol and the UI. Since DomTerm has extensible escape sequences to send and receive arbitrary data, it might make sense to start with a simple DomTerm-specific protocol and implement a UI for that. I.e. instead of sz/rz you would use a 'domterm put-file'/'domterm get-file' command. That would require installing the domterm command on the remote end, so not as convenient as sz/rz. (On the other hand, using domterm at the remote end enables detachable sessions, so that is the long-term plan anyway.) Once the UI is there, if there is demand, we can add the zmodem protocol. There are JavaScript implementations that can be used.