Practical Tmux
I feel like I'm the only one taking crazy pills whenever this topic comes up.Granted, tmux has a better configuration language.However the whole session/window/pane/instance model is bizarre, as evidenced by the secition "Multiple Clients Sharing One Session" under "common problems" in the linked article.On top of that, the below are all given as points in favor of tmux, but they're either arguably better in screen or else a wash:> Better redraw modelThis is one of the (many) things that drove me back to screen.  The two times I tried tmux, it had exactly this kind of issue where it would fail to redraw the screen correctly after SIGWINCH.> screen contents persisted through full-screen programsdoesn't this depend on whether the program calls curses endwin() function ?  why does tmux/screen need to know about this ?> not possible to remove the visual bell from Screen completelydoesn't this work?    vbell off
    bell_msg ""

though I'm not sure why you would want to do such a thing.> automatic window renaminglast I checked this used a huge amount of cpu.  is that no longer the case ?  in any case, I name my windows according to what i'm doing in that window, since "bash" or "screen" (I use nested screen sessions) or "emacs" is not a useful window title.> vertical splitsnewish screen does this.  I don't see the use.  I figure I either have a roughly 80-column screen (default linux virtual terminals) or it's wide enough to have multiple 80-column windows (laptop or desktop running X).  If I have enough horizontal space, I'm using a sensible window manager that is better-suited to real estate management.Also how does tmux handle copy/paste with vertical splits ?> vi key bindings in copy modeis this supposed to be a win for tmux over screen ? both basic emacs and vi movement works out of the box in screen.