Allow excluding windows from AeroSpace
I use Amazon Chime, and when sharing screen, there is a yellow Screen Share Border that starts jumping between the space where the Chime was open and the space that the user is sharing. This flickering is very negative experience.
Experimented a bit, but still doesn't work:
[[on-window-detected]]
if.app-id = 'com.amazon.Amazon-Chime'
run = 'layout floating'
# Later added this as well:
[[on-window-detected]]
if.window-title-regex-substring = 'Screen Share Border'
run = 'move-node-to-workspace 1'
Checklist
- [x] I've searched for duplicates. My search queries were (please don't forget to search in closed issues too):
- exclude
- disable
- Maybe related: https://github.com/nikitabobko/AeroSpace/issues/451
- [x] I've read the guide https://nikitabobko.github.io/AeroSpace/guide
- [x] I've searched in the documentation (https://nikitabobko.github.io/AeroSpace/guide & https://nikitabobko.github.io/AeroSpace/commands). My search queries were:
- disable
- exclude
- float
aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201```
Related on the Yabai side: Amazon Chime Screen Sharing · koekeishiya/yabai · Discussion #2183
I am really enjoying the tool, would be nice to cover this as well :)
~Feeling the need for this as well in regards to drop down terminal workflow~ actually the callbacks method worked fine after I found the right window id.
This feature would be great, so I can open my terminal via shortcut independent from any workspace. Right now I set the layout for wezterm to floating and I use a bash script that checks if wezterm is already open - if no, it opens in the active workspace and if yes, finds the window id, moves it to the active monitor and workspace and focuses it but it's kind of slow (2-3s). Is there a better way to do it currently?
I am excited and looking forward to this feature so that I can migrate from Yabai.
Duplicate of #2