These slides are always so out of context without hearing the audio presentation, or better, seeing the video of the presenter.. when I flip through these slideshows with the mem/macros/whatever they are called, I always imagine the audience sitting there, forced smiles, maybe a cough, and then on to the next slide.<p>These should be refactored after the local presentation. Like how episodes of The Simpsons will cull out really topical jokes that won't be funny in a month for the sake of syndication.<p>tmux is cool, and wemux is a tool we use regularly to share sessions. I am an old screen guy and appreciate that there is something similar being produced, as both products get invigorated by new features and bug fixes. I believe there is even a screenrc mode for tmux so that I can keep my muscle memory - what a great feature!
I have a feeling tmux would be useful to me, but it seems to be one of these things where all the documentation is useless unless you already understand it.<p>I understand it's a terminal multiplexer: so, on the one side, I have one or more terminals (typically pseudo; X or ssh in my case), and one or more ∗nix sessions (typically each a single process group; shells and their children like editors). In between sits tmux, with its 'sessions' and 'windows' and 'clients' and 'buffers' and 'panes'. What are these things, how are they related, and how do they correspond to ∗nix sessions and terminals?<p>Or have I got it all wrong?
<a href="http://i.imgur.com/zJGunty.png" rel="nofollow">http://i.imgur.com/zJGunty.png</a>
Since this is a post about tmux, I feel obligated to tell you about teamocil (<a href="http://teamocil.com" rel="nofollow">http://teamocil.com</a>) a small utility I wrote to automatically create sessions, windows and panes in tmux with YAML files :)
This is what I use with Tmux: <a href="https://github.com/sorin-ionescu/prezto/blob/master/modules/tmux/init.zsh" rel="nofollow">https://github.com/sorin-ionescu/prezto/blob/master/modules/...</a><p>Basically a daemon session is started (if it wasn't there before) and every terminal you open automatically connects to that session.
This means that you can close every terminal, the session is still open and new terminals will use the already existing session. As long as tmux itself isn't stopped (reboot, etc.) you'll stay in the same session.<p>Which is cool because everything is de facto detached.
By Thor, are image macros really necessary? It seems you can't have a technical presentation these days without some silly generic "memes" sprinkled all around, it's ridiculous.
I sit beside a coworker who wrestles with tmux daily.<p>He likes it, but it also frustrates him; it crashes semi-regularly, it sometimes locks out input when one program is spamming one of the tiles, and due to it intrinsic nature you can no longer select-copy large blocks of text with the mouse if you have any vertical splitters.<p>The lack of block text select-copy is alone enough to keep me away.<p>Most of the other benefits can be gotten with screen, with better reliability and performance. I use several customized .screenrcs for various tasks, to get started up quickly every reboot. But I don't run screen in every terminal because native scrollback buffer is too valuable.
I love tmux and I use for my daily work.<p>I switched from screen after reading this awesome book: <a href="http://pragprog.com/book/bhtmux/tmux" rel="nofollow">http://pragprog.com/book/bhtmux/tmux</a>
Tmux is great for working together with someone. Syme[1] uses tmux as well, and allows you to quickly program on a GitHub project with others, without setting up a server or needing to add users. I think this is relevant, as it shows the convenience of tmux.<p>[1] <a href="https://syme.herokuapp.com/" rel="nofollow">https://syme.herokuapp.com/</a>
So as a user of emacs, a user of tmux, and the soon to be recipient of a dell XPS 13 which I intend to dock at home with a very big screen and use with Xmonad... Do I need tmux?<p>It seems to fall between the gaps between easily switching between panes and applications, which you can do with Xmonad and what you can do with buffers in emacs.<p>With my previous setup I used tmux to run all my deamons (web servers I was developing on, continuous coffeescript and less building etc) in one terminal, but I'm not sure there was a huge benefit vs just opening a new terminal for each process (in hte same workspace) and using Xmonad to manage the layoutt/switching. Am I missing a trick here?
I've written a CLI (ruby gem: tmux-connector) that uses tmux to help you handle connections to multiple servers with ease. I use it on a daily basis to manage ec2 instances. <a href="https://github.com/ikusalic/tmux-connector" rel="nofollow">https://github.com/ikusalic/tmux-connector</a>
Every slide that says "tmux (screen)" should say "tmux (client)".<p>This is especially true because when people who view these slides google for more information, and they google for "tmux screen", they're gonna get rants about tmux vs screen.<p>EDIT: also, I would suggest renaming this to "elementary uses of tmux explained". Because obviously this is like 1% of the use of tmux (but the best 1% to start with, imo!)
If one likes tmux, may I recommend having a look at 'byobu'. It's built to use either tmux or screen as a backend and provides some features that make life slightly easier than using barebones tmux or screen. However, I must warn that it is just a matter of convenience and it doesn't really add anything significant.
So.. I never really understood why we need tmux/screen beyond some vanity things like running irc clients. Most applications should have sufficient log output to a file. Editing a document, want to return to it later? Save the thing.<p>Not sure I understand why people would be so excited about this tool?