Maximize Active Pane not remembering action on tmux attached windows

An older feature seems to have gone away. I use to be able to use iTerm's Tmux integration mode and use (cmd+shift+enter) to (Maximize Active Pane) on a connected Tmux session's pane.

This still functions, but if you switch from another iTerm window or tab, or alt-tab to any other apps and come back to iTerm the window has reset.

This seems to be something specifically related to Tmux integration, because it still works perfectly fine with just normal windows.

To graphically explain it, tab 0, select pane A, maximize pane, tab 1, back to tab 0, you see A and B again:

     0        1
---------|---------
|    A   |        |
|--------|    C   |
|    B   |        |
---------|---------

• iTerm2 version: 3.1.2
• OS version: 10.11.6 (OS X El Capitan)
• Attach ~/Library/Preferences/com.googlecode.iterm2.plist here (drag-drop from finder into this window) com.googlecode.iterm2.plist
• Attach a debug log, if possible. [debuglog.txt] (/uploads/2faf117bcc6d3e7d23d66d1a4c140d73/debuglog.txt)

Detailed steps to reproduce the problem:

1. tmux -CC attach
2. Select a pane and maximize it
3. Go to different tab or app, and back to original pane and it has reset the maximize setting.

What happened: Presented with original Tmux layout when coming back to window.

What should have happened: Stayed maximized in on the selected pane, like it does with the rest of iTerm windows.

What version of tmux are you using? Do you have a ~/.tmux.conf file? If so, what's in it?

changed milestone to %Next Beta

I was using tmux 2.0 tmux-2.0-2.fc23.x86_64, and I've got quite a bit in my ~/.tmux.conf so as a first step I had already tried to move that out of place and start a new tmux session to rule those out as a problem.

I went ahead and removed tmux all together and installed it again from source at the latest 2.5, and I still see the same issue.

So I came into work today and my tmux session had crashed, when I started a new one, this behavior started working like normal again. Not sure why tmux crashed, or why this stopped the problem, as I had previously restarted the whole machine to no avail.

Anyways, at least for now this looks like possibly something on the OS/tmux side of things and I'll let you know if I tickle the behavior again.

closed