Add a warning in docs about conflicts with terminal default key bindings #10380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a warning about conflicts with terminal default key bindings.
the-mikedavis
approved these changes
Apr 16, 2024
pascalkuthe
approved these changes
Apr 16, 2024
the-mikedavis
changed the title
shaleh
pushed a commit
to shaleh/helix
that referenced
this pull request
Apr 16, 2024
…ngs (helix-editor#10380) Add a warning about conflicts with terminal default key bindings.
postsolar
pushed a commit
to postsolar/helix
that referenced
this pull request
Apr 20, 2024
…ngs (helix-editor#10380) Add a warning about conflicts with terminal default key bindings.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Briefly call out to readers that some terminals may have default key mappings that aren't compatible with Helix and point them to the wiki where known conflicts are logged. I've already added a line to the Windows Terminal section about Ctrl-v bindings not working by default due to that terminal's default “Paste” binding.
Conflicting mappings were a problem for me with Windows Terminal: #10295 (comment) Since it was on the list of supported terminals in the wiki, I expected it to “just work™”, so when Ctrl-v mappings didn't, I initially raised an issue about it. Having a call-out like this, plus documentation of known conflicts on the wiki, would help users like me who encounter similar issues.