When OmniWM’s Quake terminal is focused, it should also become the focused window in macOS’s Accessibility API.
This would let skhd’s built-in focused-window matching recognize that the Quake terminal is active and apply context-specific keybindings.
Expected behavior
- Focusing the OmniWM Quake terminal updates the system Accessibility focused-window state to that terminal.
- Moving focus away updates the state to the newly focused window.
- The behavior works reliably when the Quake terminal is shown, hidden, toggled, or focused through OmniWM.
Motivation
skhd can react to the currently focused window, but it cannot execute a command to ask OmniWM for its internal focus state. Reflecting Quake-terminal focus through the standard macOS focused-window state would make OmniWM work naturally with skhd and other accessibility-aware tools.
When OmniWM’s Quake terminal is focused, it should also become the focused window in macOS’s Accessibility API.
This would let skhd’s built-in focused-window matching recognize that the Quake terminal is active and apply context-specific keybindings.
Expected behavior
Motivation
skhd can react to the currently focused window, but it cannot execute a command to ask OmniWM for its internal focus state. Reflecting Quake-terminal focus through the standard macOS focused-window state would make OmniWM work naturally with skhd and other accessibility-aware tools.