Comment by wffurr
18 hours ago
That's a totally different thing. Native macOS app vs portable terminal multiplexer. My main use case for tmux is detaching and re-attaching to a session on a remote server, for which it's extremely useful.
18 hours ago
That's a totally different thing. Native macOS app vs portable terminal multiplexer. My main use case for tmux is detaching and re-attaching to a session on a remote server, for which it's extremely useful.
I've been building a tmux wrapper that is similar you might be interested in. https://jmux.build
That's what I tell people who keep telling me to try cmux. It's false advertising to say it's like tmux. No, Zellij, sure. But not this. I will hold onto tmux forever and you'll have to pry it from my cold dead hands.
what does it add over screen which i don't even need to install?
cmux? I don't know and it's not even a good comparison.
tmux? https://www.google.com/search?q=tmux+vs+screen
If screen crashes you lose the sessions, Tmux maintains state.
Screen does not have UTF8 support, tmux does.
Otherwise just a bunch of more sane original defaults in tmux to make things much familiar.
In 2026 if given a choice between screen and tmux to use/learn, most are going to go with tmux.
> Screen does not have UTF8 support, tmux does.
“‘-U’
Run screen in UTF-8 mode. This option tells screen that your terminal sends and understands UTF-8 encoded characters. It also sets the default encoding for new windows to ‘utf8’.”
— <https://www.gnu.org/software/screen/manual/screen.html#Invok...>
“Command: defutf8 state
(none) Same as the ‘utf8’ command except that the default setting for new windows is changed. Initial setting is on if screen was started with ‘-U’, otherwise off.”
— <https://www.gnu.org/software/screen/manual/screen.html#Chara...>
1 reply →