Repository navigation
Key/Character Coding Not Being Read After Using "Less" Command #461
Description
After using the "less" command, up, down, left, right, home, and end return alphabetically characters into the buffer instead of being read as special keys.
Guessing whatever is calling into "less" is setting some sort of character encoding that is not being set back, and then the caret or escape characters are being interpreted incorrectly.
"A" is being mapped to Up, "B" to down, "C" to left, "D" to right, "H" to home and "E" to end.
Activity
andyleejordan commentedon Jan 28, 2016
Likely to due with
TERMgetting set unexpectedly.andyleejordan commentedon Jan 29, 2016
Any full-screen program executed within PowerShell causes this, e.g. vim as well.
andyleejordan commentedon Jan 29, 2016
Need to check what exactly is changing in the environment and TTY when new commands are issued, then send a repro to the CLR guys.
andyleejordan commentedon Feb 23, 2016
TERMandsttyremain the same, note added to dotnet/corefx#5902.andyleejordan commentedon Mar 1, 2016
This is also fixed by dotnet/corefx#6488. Waiting on packages.