Comment 2 for bug 1301605

Revision history for this message
PreZ (prez) wrote :

What I am asking for, is that things like the scrollback buffer and windowing that tmux has be 'exported' to the local terminal.

So if I use terminator to split screen, and it's "talking" to tmux, then that split screen is sent to tmux (so if I detached and re-attached, the same split screen would be there), and controlled locally (so clicking between splits switches windows).

The same goes for creating a new tab should be identical to creating a new pane in tmux, so that if I create 3 new tabs, and then detached tmux, re-attaching to tmux I would still have 3 new tabs (whether I connect via. terminator, or native tmux).

Finally, and most importantly, unification of the scrollback buffers. So when I use my mouse wheel to scroll, or shift-pgup/down, it shows the scroll back just like it does now - however that information comes from tmux (and is distinct per pane/split). So I don't have to do CTRL-B PgUp to scroll up my tmux buffer, and lack the controls I have from terminator - and if I use shift-PgUp it will work as expected, as opposed to being useless when using a tmux session.

But the long and short of it is, integrate with this 'control mode' of tmux so that the windowing and scrollback are unified between tmux and terminator and native terminator UI and key bindings just do their job, and affect the tmux session appropriately (and the terminator window can obtain it's state/scrollback when attaching to tmux). A local UI is much, much nicer to use than tmux via. SSH, but opening multiple terminator tabs, each having to ssh, and either each having to have their own tmux session making scrollback useless, or being suseptable to ssh disconnection problems (losing scrollback/etc) is terrible.

This is the problem iTerm2 solved by integrating with this control mode for tmux making it VERY nice to use, especially when logging into a remote session.