inxi VS Mosh

You also didn't share your hardware specs, so it's hard to figure out why that might be happening. Begin by installing the inxi tool and then run it in the terminal:

For more information about inxi and how to use it, open a terminal and enter inxi --help or man inxi. Or point your web browser to https://smxi.org/docs/inxi.htm.

https://github.com/smxi/inxi

Upon request, I can post inxi details of my laptop.

>> No, truly utilitarian websites look and function like this: https://smxi.org/docs/inxi.htm

To some extent, the majority determines what is utilitarian. Once Bootstrap achieved mass familiarity, it became utilitarian -- because almost everyone knows how to interact with it, the flow, the location of the information. The site you shared is indeed utilitarian, but it is also unfamiliar and hence makes it more difficult to find the required information at a glance.

INXI : [ https://github.com/smxi/inxi ]

The inxi script (https://github.com/smxi/inxi) can tell you this plus a ton of other stuff. Install inxi, and use something like this to run it and save the results:

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.