If I type "dir" into a console command line I see the following behaviour:
- I type "d" and nothing appears in the console (I expect to see "d" immediately following the prompt)
- I then type "i" and the "d" appears on the command line immediately following the prompt (I expect to see "di")
- I then type "r" and the "i" appears on the command line immediately following the "d" showing "di" (I expect to see "dir")
- I press return and see a directory listing as expected.
How can I stop the display lagging one character behind the keyboard?
This occurs when cmd.exe or a bash session (and presumably any other console app which takes keyboard input) when remoting into a surface pro 4 /Windows 10 from an IMAC running latest MACOS and from a Windows 10 client under parallels and from an IPAD using the Microsoft RDP client. I assume I would see the same problem from any client. All software is up-to-date as of 12-June-2017
The behaviour occurs most of the time but there have been occasions when the problem went away for no dicernible reason.
A partial workaround is to "Use legacy console" available from the console->Properties menu with a big font. This works for cmd.exe but unfortunately the bash shell won't run in this mode.