Classically, because the terminal is a grid of equally sized characters, only a single text size was supported in terminals, with one minor exception, some characters were allowed to be rendered in...
Kitty can do multiplexing over ssh as well. If you have kitty installed on the remote, you can use Kitty’s builtin ssh wrapper and get a lot of useful features.
I generally don’t either, but I do install one when using a terminal that has multiplexing. The ssh multiplexing daemon is part of the kitty binary, so it needs to be installed to work. Not really different than installing Tmux on one.
with kitty you can open a new terminal session that sets it’s cwd to the remote directory of the server you’re ssh’d into. Honestly the only thing I can think of that termux can do that kitty can’t is saving sessions
Kitty has multiplexing built in so it can also replace a lot of what tmux does (unless you’re using tmux over ssh)
That exception is my primary use case for tmux, so that explains it.
Kitty can do multiplexing over ssh as well. If you have kitty installed on the remote, you can use Kitty’s builtin ssh wrapper and get a lot of useful features.
https://sw.kovidgoyal.net/kitty/kittens/ssh/#opt-kitten-ssh.forward_remote_control
Don’t tend to have a terminal emulator of any kind installed on remote boxes. They’re headless.
I generally don’t either, but I do install one when using a terminal that has multiplexing. The ssh multiplexing daemon is part of the kitty binary, so it needs to be installed to work. Not really different than installing Tmux on one.
with kitty you can open a new terminal session that sets it’s cwd to the remote directory of the server you’re ssh’d into. Honestly the only thing I can think of that termux can do that kitty can’t is saving sessions