Mosh VS dtach

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.

ssh from your favourite terminal to your workstation works fine. (I spent two COVID years working that way.) If you use multiple terminals, look up ssh multiplexing to improve performance a bit. If you want to keep remote sessions alive without mucking up your preferred terminal, try dtach.

Not the same, but I really dig using vim (neovim) as my terminal multiplexer. Vim has tools for managing windows, splits, all the things, and it felt redundant having two separate tools.

The one thing I needed was a way to attach/detach it, and have it survive across ssh disconnects. I struggled for a while trying to use things like reptyr or others. Eventually I remembered/rediscovered dtach, which is a very thin very simple proxy, as opposed to a full on terminal emulator / multiplexer. https://github.com/crigler/dtach

Not really, and for what TRAMP + vterm doesn't cover such as unexpected disconnects, there's dtach and detached.el.

GNU Screen, tmux and dtach (with convenient Emacs interface) all serve to limit that problem.

> What's an opinion you have that most people don't agree with?

> Haha. I specialize in having opinions people don’t agree with :) In kitty, the most controversial is probably that terminal multiplexers are the devils’ gift to mankind.

I cannot agree strongly enough that the virtualized rendering done by programs like screen & tmux is a curse. Trying to get truecolor tmux+ssh+tmux+vim working in truecolor mode is a disaster. Terminal-multiplexers emulate a screen and then render their buffered session to whomever is attached, and it's a frustrating, bad, lossy process. Often the original session and what attaches don't match, and there's not much one can really do. I am not a terminal expert but the situation seems awful, & is one of the highest elder crafts of computing, far more subtle & deranged than one could ever imagine.

Kitty tries to re-build a lot of these terminal multiplexer functionalities itself. It has tabs, it has splits. Generally kitty is a pretty do-all terminal system. Afaik there's not really any way presently to solve the root of these mismatch problems, which is basically that programs generally don't reevaluate their TERM environment variable, even though these environs are technically editable at runtime (by the process, or outsiders).

Kovid (Kitty author) talks about being a vim user. I too am a vim user. In fact, one of my favorite techniques has been to just live inside vim, to use it's terminal emulator, to get ok (i'm still pretty not good) at using it's splits and windows to lay stuff out. The one missing agent for me was that I wanted a way to be able to detach my vim session & come back latter. I spent considerable time trying reptyr & other ways to reattach processes. After much failure at getting vim to detach/reattach, to persist across sessions, I eventually re-encountered a program dtach[1] I'd run into years ago, which works great. Unlike tmux and screen, it's not a terminal emulator. It's just a dumb pipe that a program can render into, and a way to reattach to that pipe again latter. It can run in detached mode so that if your session exits, the program stays open. This way, I can just open vim & have my entire workspace inside vim, with whatever terminals I need, and detach/reattach the vim session at my leisure.

[1] https://github.com/crigler/dtach

So now whenever you execute that command, it will update the channel with the current price. You can then run it on a loop, crontab, whatever you want. One of my favorite things to do is to use while $true loops, and applications like dtach.

i prefer to use dtach for that if I only need this feature