umputun / agterm / 29656914500

98%

push

github

fix: fire custom command chords from an empty window (#249)

custom command chords stopped firing once a window drained to zero
sessions. Sessions launched with `session new --command "ssh …"` close
when the connection drops, so an all-SSH window empties itself. The key
monitor gated on a focused GhosttySurfaceView, so with no surface at
first responder the chord passed through and the user's launcher chords
went dead.

the monitor now fires from a focused terminal surface, or from an agterm
terminal window whose focus is not on a text field (including an emptied
one), and passes through only for a focused text field (rename, palette,
Settings) or a non-terminal window. with no focused surface it runs the
active session if one exists, else fires a session-free launcher context
(the frontmost window id + socket) — but only for a command that does NOT
reference a session/workspace/selection token, so a session-scoped command
never runs with those tokens silently empty (an empty {AGT_SESSION_PWD}
would turn rm -rf …/* into a root glob). the same no-op covers the palette.

adds WindowLibrary.windowName(for:), CommandContext.referencesSessionScopedContext,
and XCUITests for the empty-window firing and the text-field pass-through.

7 of 7 new or added lines in 2 files covered. (100.0%)

5337 of 5470 relevant lines covered (97.57%)

5496452.31 hits per line