Key/Character Coding Not Being Read After Using "Less" Command

[ealexjordan]

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.

[andyleejordan]

Likely to due with TERM getting set unexpectedly.

[andyleejordan]

Any full-screen program executed within PowerShell causes this, e.g. vim as well.

[andyleejordan]

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]

TERM and stty remain the same, note added to dotnet/corefx#5902.

[andyleejordan]

This is also fixed by dotnet/corefx#6488. Waiting on packages.