Visor issue on multiple desktops (spaces)

Thanks for filing an issue! Please answer the questions below so I can help you.

• iTerm2 version: 3.0.14
• OS version: 10.12.3
• com.googlecode.iterm2.plist

Detailed steps to reproduce the problem:

1. Open visor via hotkey on Desktop 1
2. Go to Desktop 2 (without closing visor on Desktop 1)
3. Attempt to open visor via hotkey on Desktop 2
4. Nothing appears

What happened: The visor remains open and will not move to a new desktop when called if previously opened in a separate desktop.

What should have happened: The visor should have moved to the active desktop when activated via hotkey. It should be the same instance, not a new window opened. So it should move the window from the previous desktop (regardless of whether open/closed) and open it on the current one.

I'm a migrant from TotalTerminal, and it's deeply embedded into my workflow. The above method is how TotalTerminal dealt with the visor. I understand if it isn't possible, but if it is and I'm missing it I'd greatly appreciate any help.

Seems Prefs > Profiles > Default > Space is set to Current Space, which means it's bound to the space where it was first opened. Perhaps All Spaces would be a better setting for your workflow? Or were you looking for a setting that would have it follow you from space to space on each opening? That might be a reasonable reinterpretation of Current Space for the hotkey window, since a similar change was made for Screen with Cursor.

changed milestone to %Next Beta

I might enable it for All Spaces, but since I'm working off a laptop it takes up quite a bit of screen real estate having it open on every window.

But you're correct, I was hoping there was already a way baked in that would open it on the current space, regardless of whether it's already in another space, on hotkey press.

I appreciate the response. It's really remarkable given the size of your user base you're continuing to engage so directly with users.

closed

Turns out to be really easy to make it switch to the current space, and the behavior is much nicer! Fixed in commit 2d390f5d.