Closed
Description
Description
See the following code:
using System;
var key = Console.ReadKey(true);
Console.WriteLine("KEY: " + key.Key);
Console.WriteLine("MODS: " + key.Modifiers);
Run it with dotnet run
and hit ENTER.
NOTE: You may need to SPAM hitting enter as I see this Ctrl
+J
behavior only when the process is under strain...
Configuration
- Which version of .NET is the code running on? .NET 5 RC1
- What OS and version, and what distro if applicable? macOS Catalina
- What is the architecture (x64, x86, ARM, ARM64)? x64
- Do you know whether it is specific to that configuration? No. It could be others. Not sure.
Regression?
Yes this worked before. It worked in .NET 5.0 preview 7. Then a similar bug showed up in .NET 5.0 preview 8 (except it was Ctrl+Enter instead of Ctrl+J)...
Other information
This was discovered in PowerShellEditorServices. The end result is the user hit's ENTER in the PowerShell Integrated Console and the console does nothing making the console useless.