GNU screen was released in 1987.
tmux was created in 2007.
I've used mosh a lot but it's just interesting to note it's in the same category as screen and tmux
I basically don't use ssh at all any more for interactive sessions, because I'm sick of a few lost packets on wifi or a weak cell signal dropping my connections and forcing me to start over.
Tmux, I used to use and eventually abandoned. I decided I didn't need two keyboard-based window managers (I use Spectacle on Mac) and the one that was only for shells was the one that could go. I have replaced it with nothing, so far, aside from that I just open more Terminal.app windows now (I also used to use iTerm2, for years, until it dawned on me that I was using exactly nothing in it that's not also provided by Terminal.app, and the latter's got better input latency, so I was suffering an extra installed program and slightly less responsive typing for no reason at all)
I leave with the laptop, return days later, and perform no manual intervention to reconnect. It's absolutely brilliant.
I connected to a public Unix server and read news, IRC'ed, IM'ed and such like crazy. Also, without being connected to a Pubnix, IRC and Gopher did it fine, the web with patience, and the same with Gemini (gemini://gemi.dev has been really useful to read news and scrap a 95% of unneeded scripts and trackers from web sites).
Usenet was slow on fetching, but totally readable the next morning, and, better, offline.
alias looptmux='while true; do ssh tmux; sleep 2; done' autossh -M0 tmuxSo you're saying you're a masochist
I use tmux now because it’s supposed to be cool but secretly like gp I also wonder what the actual difference is , besides a different default leader key. Oh and killer iterm2 integration.
(0) - main: 6 windows
(1) ├─> 0: elvish-
(2) ├─> 1: elvish*: "[mosh] embee@foo:~"
(3) ├─> 2: elvish
(4) ├─> 3: elvish: "embee@bar:~"
(5) ├─> 4: elvish: "[mosh] embee@fedora:/etc"
(6) └─> 5: elvish
(7) - local: 6 windows (attached)
(8) ├─> 0: elvish
(9) ├─> 1: elvish-
(M-a) ├─> 2: [tmux]*
(M-b) ├─> 3: elvish
(M-c) ├─> 4: elvish
(M-d) └─> 5: elvish
(M-e) - dev: 7 windows (attached)
(M-f) ├─> 0: elvish*
(M-g) ├─> 1: elvish-
(M-h) ├─> 2: elvish
(M-i) ├─> 3: elvish
(M-j) ├─> 4: elvish Host tmux
HostName 1.2.3.4
IdentityFile ~/.ssh/etc.etc.etc
RequestTTY force
RemoteCommand screen -dR
Edit: I guess it's missing the iTerm integration unbind-key C-b
set -g prefix C-Space
bind-key C-Space send-prefix
I find it a lot easier to type than either Ctrl-A or Ctrl-B.In any case with your bindings you can still C-z z and it sends C-z to the process.
The author of this feature also ported it to the Windows Terminal.
Besides, Chrome OS’s built in terminal also has tmux integration.
Would love for examples using Windows Terminal as well.
Note: that Terminator I linked is a re-boot (I'll be back) so, I might give it another go as well.
I wanted it to be better, and might go back if I could figure out the font issues, but I just don't have the time right now.
Interesting, I've been using exactly that combination for ... as long as tmux and iTerm2 have been around?
I am not aware of any color or font issues. What am I missing?
Does everything still go "through" tmux (so parsing etc. is still done twice), or does iTerm handle most of the rendering and just delegate scrollback storage/session persistence to tmux? The latter seems like the best of both worlds.
I am a former Kitty user and current Ghostty user and hope Ghostty stays basic and good.
Edit: It appears to be related to iterm2's tmux integration. Neat.
A lot of these arguments against tmux seem like they're more relevant to someone developing a terminal rather than using it. It's fine for people working on their own terminals to decide they don't care to support it, but I don't really find the arguments convincing as something I should care about, and I'd personally just switch to another terminal with better support for it rather than stop using it.
With this in my `~/.ssh/config`, I can just type `ssh tmux` to get back to my remote dev box whenever I wake my computer or change connections.
With iTerm2's tmux integration enabled, this will pop open a new window where the remote tmux tabs and scroll buffer look and act just like native, local iTerm2 tabs and scroll buffer. I don't even know any tmux commands.