(re)connected tmux sessions' windows overlap existing fullscreen windows in the same OSX space

iTerm2 currently pops up new tmux windows after session (re)attachment in front of the previously focused full-screen terminal, effectively stacking two full-screen windows in one space, with only one being the "primary" owner of that space.

I have to manually unfullscreen the new tmux window (Cmd-Enter) and re-fullscreen it to get it to migrate into its own OSX space.

After that procedure, making new windows in that tmux session using Cmd-N allocates them into new Spaces as expected (and like most other OSX apps).

I have "Native full screen windows" enabled, and all profiles including 'tmux' are configured to be fullscreen.

iTerm 2.9.20160131-nightly OSX El Capitan 10.11.3 com.googlecode.iterm2.plist

NSWindow.collectionBehavior's .canJoinAllSpaces and .fullScreenAuxillary have been culprits for this in my own apps. I understand why hotkey and switcher panels may have these properties but terminal windows never should if "native full screen windows" is enabled.

Hmm, the Screen: and Spaces: settings of my 'tmux' and Default/whatever profiles may have something to do with this. Investigating..

Here's what I did to try to reproduce (using your config file):

1. In a native fullscreen window, run tmux -CC
2. That window minimizes into the dock
3. A tmux window opens on the main desktop in non-native fullscreen (oops, this is a bug, but not the bug you described)

I suspect the problem may be related to opening multiple fullscreen windows at once, not to mention opening windows while a fullscreen window is miniaturizing. These operations have to be done serially. I can't believe this state of affairs has lasted since 10.7 :(

Milestone changed to Ship 3.0

Thanks for looking into this, I think you're right about the serialization. Might it be possible to mitigate this by injecting delays in the auto-minimize or maybe in my custom commands?

I forgot to post my Dynamic Profiles, for reference:

{ 
  "Name" : "Default",
  "Guid": "Default",
  "Description" : "Default",
  "Default Bookmark" : "Yes",
  "Tags" : [
    "localhost"
  ],
  "Working Directory" : "~",
  "Blinking Cursor" : true,
  "Disable Window Resizing" : true,
  "Sync Title" : false,
  "Prompt Before Closing 2" : false,
  "BM Growl" : true,
  "Command" : "\/usr\/local\/bin\/bash",
  "Description" : "Default",
  "Mouse Reporting" : true,
  "Screen" : -2,
  "Custom Command" : "No",
  "Window Type" : 1,
  "Close Sessions On End" : true,
  "Terminal Type" : "xterm-256color"
},
{
  "Tags" : [
    "tmux"
  ],
  "Name" : "tmux",
  "Guid" : "tmux",
  "Prevent Opening in a Tab" : false,
  "Dynamic Profile Parent Name": "Default"
},
{
  "Tags" : [
    "tmuxgw"
  ],
  "Name" : "tmuxgw",
  "Guid" : "tmuxgw",
  "Window Type" : 0,
  "Screen" : -1,
  "Space" : -1,
  "Prevent Opening in a Tab" : true,
  "Default Bookmark" : "No",
  "Dynamic Profile Parent Name": "Default"
},
{
  "Tags" : [
    "tmux",
    "localhost"
  ],
  "Command" : "\/usr\/local\/bin\/bash -l -O expand_aliases -c \"TMUXCC=1 \/usr\/local\/bin\/tmux -u -q -CC new-session -D -A -P -s localhost\"",
  "Custom Command" : "Yes",
  "Name" : "macmux",
  "Guid" : "B5723993-9861-4FF0-982A-1805731F0EC0",
  "Prevent Opening in a Tab" : true,
  "Default Bookmark" : "No",
  "Dynamic Profile Parent Name": "Default"
}

Most of my "daily driver" profiles are inheriting from tmuxgw, like macmux. They usually ssh somewhere and run tmux -CC. They are normal-window all-spacers so I can interact with any of SSH's login prompts.

I do sometimes see an odd behavior when the tmuxgw auto-minimize starts after session attachment: The window (#2 (closed) in example example screenshots) becomes maximized and only shows a blank grey background and a titlebar.

Commit b22e4299 adds support for native fullscreen tmux windows and serializes opening them one at a time. It's off by default since it's a risky change, but you can enable it by turning on Prefs > Advanced > When opening multiple fullscreen windows, enter fullscreen one window at a time. Please let me know if you experience any issues.

This change will be available in the next nightly build (about an hour from now).

There is one known problem, which is that if you try to switch spaces while it's fullscreening windows, it will beep and fail to enter fullscreen. I think this is an OS limitation I can't work around.

Seems to be working, I am not getting stacked fullscreen anymore. Wow, thanks!

Status changed to closed

Milestone changed to Feature Complete 3.1

I'm going to reopen this to make it the default behavior in version 3.1.

Status changed to reopened

This is now on by default.

closed