Open ELLIOTTCABLE opened 1 week ago
However, if there's a monitor with no windows on it, then when you focus-monitor onto that empty monitor, there's no integration with the system. (The wrong monitor's menubar is highlighted, ⌘␣ will open windows on the wrong monitor, etc.)
This is also the case when using workspace x
to focus on a particular monitor, however I don't have any issues with applications opening on the wrong monitor. I've tested using spotlight and raycast (which is what I daily drive) and those work as expected even when the menubar isn't highlighted correctly. I also tested using workspace x
and also focus-monitor right
with no applications on my secondary monitor and applications still open up on whatever monitor is focused in aerospace (ie. the asterisked workspace in the menubar)
focus-monitor
is great (Aerospace has really come a long way!); but at the moment, it's got one glaring flow issue.When all monitors have at least one window, cycling through them with a
focus-monitor left
command or similar also drags the macOS "focus" along (that is, the top menubar is faded out on the other, non-focused displays; and ⌘␣ pops up a search window on the correct monitor.)However, if there's a monitor with no windows on it, then when you
focus-monitor
onto that empty monitor, there's no integration with the system. (The wrong monitor's menubar is highlighted, ⌘␣ will open windows on the wrong monitor, etc.)This is slightly worse when
borders
or similar is installed - now, the 'active window' indicator is no longer doubling as a "what display/container AeroSpace is going to operate on" indicator.One janky fix, is to rewrite the default
on-focused-monitor-changed = ['move-mouse monitor-lazy-center']
hook to also …Thus, I suppose, at least one potential "fix" for this might be to make that behaviour the default (hopefully a lot) faster than indirecting through a shell, especially when tabbing through monitors quickly.
Checklist
focus-monitor empty
"focus-monitor"