Workaround kitty F3 issue #2740
Closed
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
|
This is a workaround/fix for #2720 |
|
taking a look at it now (finally!), sorry about the lengthy delay |
|
wow, we sure don't pick up F3 correctly! good find |
|
verified in |
|
Merged via #2825. Thank you for your contribution to Notcurses! |
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.
Notcurses does not recognize the F3 key correctly in kitty (and ghostty, maybe others?).
These are some workarounds I've had lying around in my local tree for a few months that resolve the issue for me. Really, really not sure about the quality and/or correctness of these fixes though. I have not spent too much time looking at the inner workings of the notcurses input layer and these changes are just enough to get it working for me.
Comments are very welcome.