You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like when running move-node-to-monitor, focus stays on the next available windiw of the original workspace. If there are no more windows, Aerospace loses focus of any window.
I'd expect the focus to stay on the moved window (maybe this is related to #186).
Seems like when running move-node-to-monitor, focus stays on the next available windiw of the original workspace. If there are no more windows, Aerospace loses focus of any window
It's exactly how it works and it's by design. move-node-to-monitor performs one and only one operation - move the window to the target monitor, the command shouldn't change the focused workspace.
You can make focus follow the window by using focus-monitor as you described (not sure why you call it "hacky"). focus-monitor will focus the most recently "used" window on the target monitor, that's why it works.
#186 suggests that there should be a --focus-follows-window flag to enable focus-following
Thanks @nikitabobko, appreciate the time you've put into this great tool!
I mentioned "hacky" because it wasn't apparent (at least to me) that changing focus to another monitor would focus on the newly-moved window.
I agree that --focus-follows-window is a good implementation, didn't see it mentioned specifically for move-node-to-monitor, so I wasn't sure if you were planning it on supporting that.
Seems like when running
move-node-to-monitor
, focus stays on the next available windiw of the original workspace. If there are no more windows, Aerospace loses focus of any window.I'd expect the focus to stay on the moved window (maybe this is related to #186).
How to reproduce:
If this is not really what's expected, I'd expect at least to be able to use the
focus
command on a specific window id, so that I could doHacky workaround currently, maybe someone finds this useful. I usually only use (at most) 2 monitors, so I'm doing this:
The text was updated successfully, but these errors were encountered: