closed windows are sometimes not detected

ianyh / Amethyst

Automatic tiling window manager for macOS à la xmonad.

https://ianyh.com/amethyst/

MIT License

14.88k stars 485 forks source link

closed windows are sometimes not detected #85

Closed simon-weber closed 7 years ago

simon-weber commented 11 years ago

I can replicate this by:

opening chrome
opening iterm2 (iterm2 now has focus)
closing my iterm session with ^d (iterm2 window closes)

After doing this, I expect chrome to have focus, but it does not. Doing one clockwise switch gives chrome focus, making it seem that Amethyst thought iterm2 was still supposed to have it. Doing another switch keeps focus on chrome.

Trello Card

ianyh commented 11 years ago

This is actually an OS X behavior, not an Amethyst one. We could theoretically ensure that there's always a focused window. I am having trouble coming up with any reasons that would be bad, but it might be worth further discussion.

simon-weber commented 11 years ago

Gotcha. I'm new to os x, so this is news to me =)

I'd definitely support always having a focused window -- that's what I've come to expect from xmonad.

dhgwilliam commented 11 years ago

Can we tell the difference between Finder-w/o-windows ("unfocused") and Finder-windows? If so, then I see no reason to ever give focus to Finder w/o windows. Or rather, I'm sure there are reasons but I imagine they don't apply to a twm-workflow...

ianyh commented 7 years ago

Closing. See https://github.com/ianyh/Amethyst/pull/591