3 ms·
Does tmux integrate with itself? That is, does this solve the problem of needing different prefix keys when nesting tmux sessions (whether using iTerm2, or usin
by mooism2 12y ago
Does tmux integrate with itself? That is, does this solve the problem of needing different prefix keys when nesting tmux sessions (whether using iTerm2, or using a terminal emulator that doesn't itself integrate with tmux)?
- cooper12 12y agoI thought that, when nesting tmux instances, you just press the prefix key a number of times depending on how deep you need you need your next keystroke to propagate? For me personally, I use ctrl-a instead of ctrl-b so I have this line in my ~/.tmux.conf: #send prefix to nested sessions with C-a bind-key C-a send-prefix Lastly, iterm2 uses it's own keystrokes for it's tmux integration. (i.e.: cmd-D to split vertically)
- mooism2 12y agoI have tmux set up so that pressing the prefix key twice switches to the previously selected window. I don't remember whether it was like that out of the box, or whether I had to configure that when I switched from gnu screen. I take it with nested tmux sessions, cmd-D would split the outer tmux window? How would you split the inner tmux window?
- cooper12 12y ago> I don't remember whether it was like that out of the box, or whether I had to configure that when I switched from gnu screen. It's worth checking your config file out. And I'm not sure how to answer your question because the way iterm integrates with tmux is that it allows you to create split panes with their own bash sessions. If you want to run tmux in those sessions, it would be tmux running in that pane, but textually instead of graphically. Here's a screenshot to make things more clear: http://i.imgur.com/0hmw62I.png http://i.imgur.com/0hmw62I.png cmd-D would just create another pane to the left.