Allow configuring enhanced keyboard protocol detection #7020
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This can be used to force Helix to enable or disable support for the enhanced (Kitty) keyboard protocol. Force disabling support can be useful if you rely on ambiguous escape codes (C-[ is suprisingly popular). Force enabling this can be useful to avoid any overhead of the automatic detection, though this is usually unnoticeably small.
This fixes #6551 but I think the proper way to support that workflow is to enable rebinding Escape in remaining places (#5505). I'll open this so anyone who wants to can use the changes but I'm not sure this should actually be merged.