Tmux, for fun and profit

I am going to go out on a limb and say this article has little to no content. I am surprised that it has 69 points despite being very light on content.<p>More over, the comments here are mostly tangential to the article (except in the sense that they involve the word tmux).<p>Am I totally wrong? Can everyone else see into this article where I can't?

I found this to be a far superior article: <a href="http://news.ycombinator.com/item?id=3824399" rel="nofollow">http://news.ycombinator.com/item?id=3824399</a>

This post got me thinking about building a remote dev system using tmux running on EC2 or some other cheap VPC host. I like the idea of pulling up a fully configured dev system from anywhere. Mainly so I can pick up the same session from home or work for hacking on my own projects, rather than keeping two separate systems in sync.<p>Does anyone else do something like this?

My comment from the blog post:<p>tmux and screen both have upsides and downsides for pair programming. Ones that I know of:<p>1. screen requires itself to be setuid root for session sharing. This is security issue to say the least. The frustrating part of this is that screen <i>explicitly checks</i> that that uid == 0. This means that, even if you can iron out all of the permissions issues between you and your partner without needing root access, screen will only accept suid root as the solution.<p>2. When you are screen sharing in tmux, the configuration used is the configuration of the person hosting the session. This can suck if you have a lot of non-standard bindings, because it forces the person you're pairing with to know them too. screen allows you to both use your own configurations while being connected to the same session.

I've used tmux and screen on occasion, but I can't get past the fact that they don't fit well with GUI terminals. I love having "GUI" scroll-back, which I can go through with mouse scroll-wheel, or just dragging the scroll bar up and down.

This is cool and something I didn't know about tmux:<p><i>"The one disadvantage of everyone at DockYard working remotely is that you can't just turn around and ask someone to come to your desk to pair up. Tmux allows multiple users to connect to a specific session. With a bit of dynamic DNS magic, port forwarding, and ssh tunneling, multiple people can connect to the same tmux session, work in the same vim window, and see the same development server."</i><p>...<p><i>"With a tmux, ssh port forwarding, and Google+ Hangout, you can create a useful pair programming environment with your remote coworkers. We find this setup very effective and use it often to work together and tackle an issue."</i>

Just out of curiosity and without creating yet another HN Poll; Who prefers Tmux over Screen and why?

Can someone please explain why dynamic DNS, port forwarding and SSH tunneling involved when attaching to the same session?<p>I just fired up two instances of Putty and see my keystrokes replicated within a second.

Does Mosh (posted yesterday) support multiple connections? I know it can suspend resume like screen/tmux. Seems like it would be preferable if it does.

``Mouse free environment'' is a retarded concept.<p>And that book doesn't understand anything about tmux and why it came about.