Hacker News new | past | comments | ask | show | jobs | submit login

As someone who already has a screen session setup, with bindings and a status bar, and auto-creating screens, is there anything tmux brings to the table?



I've been using screen for years. All my terminal sessions are within one or two screen sessions. So I'm probably in a similar situation to you: I'm used to it, I have it customised to how I like it, and it "just works".

I recently switched to tmux and after several weeks of testig it out I think I'm going to make the change permanent.

It is actively being developed (screen is currently stagnant), it has a much greater scripting capability, it is rock solid, its region-splitting capabilities is hugely better than screen's (that is the single reason I switched to tmux initially).

On the con side: it seems you have to use the metakey to enable the scrollback buffer. I really hate that, but now I've used it for a while I'm used to it and it is not as annoying as it was at first. (I'm always using 'ls' in a terminal and I invariably want to scroll up to see the first few entries. With screen I could just shift-PgUp, with tmux I do ctrl-A, PgUp. It's ok.)

Other than those things, tmux seems to do everything screen can do in terms of resuming sessions and so on.

The enhanced region splitting makes it superior for my use, so I will stick with tmux.


I used screen for a while and then switched to tmux for the same reason (region splitting). These days, I am not even using tmux anymore and just using emacs with new buffers running eshell. Serves me well.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: