-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Resolution-ExternalThe issue is caused by external component(s).The issue is caused by external component(s).WG-Interactive-PSReadLinePSReadline related issuesPSReadline related issues
Description
Steps to reproduce
- Open an ssh connection using PuTTY (keypad setting is "Normal", login shell is bash)
- Ensure the numeric keypad works (
0-9,/*-+.andEnter) - Run pwsh
- Try the numeric keypad keys again
- Exit pwsh (whether via
Ctrl-Dorexit) - Try the numeric keypad keys once more
Expected behavior
- Keypad keys work the same in pwsh as in bash (just like they do in ksh, dash, ...)
- Keypad keys still work when returning to bash from pwsh
Actual behavior
- Only the
Enterkey works normally./*-do nothing,+insertsl, and0-9insertp-y. - All keypad keys (including
Enterare non-functional in bash when returning from pwsh.
That PowerShell doesn't handle the keypad is one thing, but that it messes it up for everyone else is Real Bad(tm). It also means that it's not a case of just reading things differently - it seems to be changing the tty's mode without changing it back on exit.
Environment data
Name Value
---- -----
PSVersion 6.2.2
PSEdition Core
GitCommitId 6.2.2
OS Linux 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15)
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Metadata
Metadata
Assignees
Labels
Resolution-ExternalThe issue is caused by external component(s).The issue is caused by external component(s).WG-Interactive-PSReadLinePSReadline related issuesPSReadline related issues