-
Notifications
You must be signed in to change notification settings - Fork 351
Missing support for DECCKM cursor keys #341
Comments
Another option here is for survey to explicitly disable DECCKM mode on startup so that they key behave the way it wants! Sending |
Hey @wez - thanks for reporting this! I'm not sure I will have the time to add support for DECCKM but if you wanted to take a shot, i would love to support you however I can. Feel free to reach out on the gophers slack :) That being said, if you could find the time to disable the mode, it would be much appreciated! |
I don't have time to do that, however: |
We had a user with this issue today on macOS, it seems the |
PowerShell 7.2.0-preview.8 no longer exhibits this issue. |
What operating system and terminal are you using?
cli/cli#3071 has more context, but:
gh auth login
What did you expect to see?
The cursor keys should navigate to select one of the login options
What did you see instead?
could not prompt: Unexpected Escape Sequence: ['\x1b' 'O']
Analysis
Due to PowerShell/PowerShell#12268 powershell enables DECCKM which changes the cursor key encoding from
CSI A..D
toSS3 A..D
instead. SS3 is encoded asESC O
in 7-bit encoding.It is technically a bug that powershell leaves the cursor keys in that mode.
However, it should be pretty simple to support this encoding here in survey:
survey/terminal/runereader_posix.go
Lines 79 to 81 in dbdb3e5
by allowing either
[
orO
The text was updated successfully, but these errors were encountered: