Numpad enter doesn't behave the same way as regular enter in certain situations #10451
-
Issue DescriptionNumpad enter doesn't function in opencode. First reported here: anomalyco/opencode#7698 It's unclear if it's a Ghostty or opencode issue, but opencode recognizes numpad enter fine in other terminals on the same systems for multiple people, across macOS and Linux. The terminal keyboard inspector shows nothing out of the ordinary. Opening this to try and figure out the next steps to diagnose from either side. Expected Behaviornumpad enter should behave like regular enter in opencode Actual Behaviornumpad enter is a no-op within opencode Reproduction Steps
Ghostty LogsGhostty VersionOS Version Information6.18.3-arch1-1 (Linux only) Display ServerX11 (Linux only) Desktop Environment/Window ManagerPlasma/KWin Minimal Ghostty Configuration# (no additional configuration)Additional Relevant ConfigurationNo response I acknowledge that:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
this is not a ghostty problem like you noted the terminal inspector and programs like kitten show-key register now if opencode supports kitty keyboard protocol that is entirely their fault below is the output of like i stated above in non kitty mode enter and numpad enter are the exact same this seems to suggest it has some concept of kitty keyboard protocol another note some of the programs in that issue mentioned to "work" like gnome terminal do not support kitty keyboard protocol |
Beta Was this translation helpful? Give feedback.
this is not a ghostty problem like you noted the terminal inspector and programs like kitten show-key register
enterandnumpad_enterexactly the samenow if opencode supports kitty keyboard protocol that is entirely their fault below is the output of
kitten show-key -m kittylike i stated above in non kitty mode enter and numpad enter are the exact same
https://github.com/anomalyco/opencode/blob/23d85f47397c594e62929682b27835099b788fdf/packages/opencode/s…