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
Context-specific TUI actions can share a physical key with global or managed-textarea bindings. PR #42366 fixes the observed Shell-tab failure by giving the default Ctrl+D binding first refusal, but the mechanism is deliberately literal and local:
A user rebinding composer.shell.kill to another editor-owned key can recreate the same precedence bug. Other textarea-backed contextual surfaces may have the same class of issue but do not yet have collision tests.
Composer navigation and configured non-default bindings while an editor remains focused
Desired direction
Provide a reusable, configuration-aware way for an active contextual layer to take precedence over global/editor bindings. Avoid per-component raw-event checks for one literal default shortcut.
Acceptance criteria
Contextual commands can claim their configured bindings without hard-coding physical keys.
Disabled (none) bindings remain disabled.
Multi-binding and rebinding behavior is preserved.
Focused textarea editing still wins when no active contextual command claims the key.
Add collision tests for the affected composer and textarea-backed surfaces above.
Activity
Tarquinen commentedon Oct 20, 2026
This was fixed by #42384. That PR merged into the
v2branch, so GitHub didn't close this issue automatically. Closing as completed.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊