- `tmux server` is the 'backend' process listening on /tmp/pairprog
- `client0` and `client1` are the 'frontend' processes connecting to the socket /tmp/pairprog.
- `session` is the collection of windows that you are using.
The issue is that the currently active/focused window is an attribute of the session, meaning that all connected clients are always focused on the same window. What if you want to have each client focus on a separate window? This is behaviour that you get by default in screen, but you have to work a little more for in tmux.
The script is just a simple way to use session grouping, which would look like this:
Note the '=' between the sessions. I'm using this to denote that `session` and `session-1` are grouped, meaning that they share the same windows. Since each client is connected to a different session, they can switch windows independently.
It's one reason I hadn't used tmux before, i couldn't figure out a nice way to get this. I love to use screen this way on multimonitor setups, and tmux's other windowing features would make this awesome.
- `client0` and `client1` are the 'frontend' processes connecting to the socket /tmp/pairprog.
- `session` is the collection of windows that you are using.
The issue is that the currently active/focused window is an attribute of the session, meaning that all connected clients are always focused on the same window. What if you want to have each client focus on a separate window? This is behaviour that you get by default in screen, but you have to work a little more for in tmux.
The script is just a simple way to use session grouping, which would look like this:
Note the '=' between the sessions. I'm using this to denote that `session` and `session-1` are grouped, meaning that they share the same windows. Since each client is connected to a different session, they can switch windows independently.