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
Tmux has probably some specific features Kitty won’t do as good as a native multiplexer? (sorry I’m not the right person to ask this question :s) but It has the features I’m looking for without the need to install one.
It was quite cumbersome to configure a terminal + a multiplexer on MacOS to behave how I liked it. Kitty solved this issue while being fast, simple and a lot of customization in one single app.
One feature that was really important, copy/past over SSH with Micro which involved quite a hacky thing with iTerm2 + Tmux.Also being able to split my windows, create tabs…
But as I said I have only basic use cases and can’t really say If Kitty’s multiplexing features are on par with Tmux. However, during my web search I read about a lot of people far more knowledge than myself who actually switch to kitty from Tmux without regrets !
As a non-user of kitty, why did it make you drop tmux? Don’t they do different jobs?
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
Tmux has probably some specific features Kitty won’t do as good as a native multiplexer? (sorry I’m not the right person to ask this question :s) but It has the features I’m looking for without the need to install one.
It was quite cumbersome to configure a terminal + a multiplexer on MacOS to behave how I liked it. Kitty solved this issue while being fast, simple and a lot of customization in one single app.
One feature that was really important, copy/past over SSH with Micro which involved quite a hacky thing with iTerm2 + Tmux.Also being able to split my windows, create tabs…
But as I said I have only basic use cases and can’t really say If Kitty’s multiplexing features are on par with Tmux. However, during my web search I read about a lot of people far more knowledge than myself who actually switch to kitty from Tmux without regrets !