A tmux crash course (2016)
robots.thoughtbot.com
A tmux crash course (2016)
1–10 of 13 posts
Re: A tmux crash course (2016)
#2Zoom is the best command, after using tmux for years, just discovered it. Ctrl-b z brings a pane into full screen and back. I use a 4x4 grid and zoom in and out.
Re: A tmux crash course (2016)
#3I often use screen within tmux as it's easier with ctrl A and ctrl B than double of those.
Re: A tmux crash course (2016)
#4I often use screen within tmux as it's easier with ctrl A and ctrl B than double of those.
You can configure your local tmux to have a key press send the prefix command to a remote tmux with a single keypress.
For example, to bind C-a to control the remote session:
bind-key -n C-a send-prefixRe: A tmux crash course (2016)
#5I often use screen within tmux as it's easier with ctrl A and ctrl B than double of those.
I suppose you mean that you run tmux locally and then you ssh into a server and run screen remotely?
If so, I wonder how hard it would be to make tmux into a client of itself using control mode. I only learned about control mode when I discovered iTerm2's tmux integration, whereby remote tmux windows materialize as "actual" terminal windows on my desktop. However, for the same reason that iTerm2 can resize a window, create a new one, show and hide them, etc, I would _imagine_ it's possible to have your remote tmux windows materialize as tmux windows in your local tmux, and thus would be managed using only a single prefix key.
I would guess such a capability would need to be baked into tmux, but I actually wonder how much code would actually be required, since control mode already exists and clearly works quite well.
Re: A tmux crash course (2016)
#6I often use screen within tmux as it's easier with ctrl A and ctrl B than double of those.
I suppose you mean that you run tmux locally and then you ssh into a server and run screen remotely? If so, I wonder how hard it would be to make tmux into a client of itself using control mode. I only learned about control mode when I discovered iTerm2's tmux integration, whereby remote tmux windows materialize as "actual" terminal windows on my desktop. However, for the same reason that iTerm2 can resize a window,…
ssh to remote server over VPN then tmux attach, then connect to target machine and launch screen to work multiple sessions on target machine as it's not networked.
Re: A tmux crash course (2016)
#7I often use screen within tmux as it's easier with ctrl A and ctrl B than double of those.
You can configure your local tmux to have a key press send the prefix command to a remote tmux with a single keypress. For example, to bind C-a to control the remote session: bind-key -n C-a send-prefix
Binding isn't an option as only defaults are available on target machines (can't save .screenrc file). There can be thousands of target machines so binding doesn't scale.
Re: A tmux crash course (2016)
#8I'm just curious- as I haven't really been able to get into tmux. Why use it as opposed to iTerm's built-in tabs and panes? Or like what are the selling points outside of just tabs and panes?
... I mostly just want to be sold on it :)
Re: A tmux crash course (2016)
#9I'm just curious- as I haven't really been able to get into tmux. Why use it as opposed to iTerm's built-in tabs and panes? Or like what are the selling points outside of just tabs and panes? ... I mostly just want to be sold on it :)
My initial attraction to screen / tmux was when I spent most of my time logged into remote servers. The ability to start a long-running script at the office, detach from screen, then re-attach at home to check on it later was indispensable.
Re: A tmux crash course (2016)
#10I'm just curious- as I haven't really been able to get into tmux. Why use it as opposed to iTerm's built-in tabs and panes? Or like what are the selling points outside of just tabs and panes? ... I mostly just want to be sold on it :)
My initial attraction to screen / tmux was when I spent most of my time logged into remote servers. The ability to start a long-running script at the office, detach from screen, then re-attach at home to check on it later was indispensable.
Can you do this with traditional commands? Disown detatches from the terminal (if I remember correctly), is there an equivalent to re-atach it later?