Conditionally disable keybindings when they wouldn't do anything

Discord username (optional)

No response

Describe the solution you'd like?

When a full-screen application is running, e. g. a text editor or a file manager, certain keybindings don't make sense, e. g.:

• Navigating between blocks or favorites
• Working with the command editor
• Clearing the screen
• Copying command and/or output

Those keybindings are likely to be in conflict with those configured for the currently running application.

Proposed solution:
When not working with the prompt but instead in a full-screen application, conditionally disable those keybindings so they can be used from within the running application.

Is your feature request related to a problem? Please describe.

I want to keep using Option+Up/Down to move lines up/down in the micro editor (default keybinding). In Warp, this keybinding doesn't work by default because it's also assigned to navigating between favorite blocks. This doesn't work anyway when micro is running since no blocks/favorites are shown then.

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

Start by tracing how Warp handles keybindings while a full-screen application is running, using the listed navigation, command-editor, screen-clearing, and copy bindings as cases. Done means those bindings no longer intercept input when the prompt is not active, while they continue to work at the prompt.