.NET 5 fails to read the HOME key on ubuntu16.04

[bagajjal]

VTSequence for Home is ^[[1~.
bash is able to recognize this VTSequence. .NET fails to recognize the VTSequence.
TERM used is xterm.

I haven't tried the older versions of .NET. But I guess it exists on the older .NET versions as this is a fundamental issue.

Below screenshot captures all the details

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @eiriktsarpalis, @jeffhandley
See info in area-owners.md if you want to be subscribed.

---

Issue meta data

Issue content:
	VTSequence for Home is ^[[1~. bash is able to recognize this VTSequence. .NET fails to recognize the VTSequence. TERM used is xterm. I haven't tried the older versions of .NET. But I guess it exists on the older .NET versions as this is a fundamental issue. Below screenshot captures all the details </td>
Issue author:		bagajjal
Assignees:	-
Labels:	`area-System.Console`, `untriaged` </td>
Milestone:	-

[eiriktsarpalis]

I'm able to reproduce using PuTTY. Seeing the same issue with function keys F1-F4 (^[[11~ - ^[[14~), however F5-F12 (^[[15~ - ^[[24~) are mapped correctly. The Insert (^[[2~) and Delete (^[[3~) keys are also mapped correctly.

Note that other terminal emulators I tested (Windows terminal, xterm, gnome terminal) all map the Home key to ^[OH which is interpreted correctly by Console.ReadKey(). Same is true for function keys.

As a side note, it looks like Ctrl+Home is broken in all terminals that I tested. Related to #802.

[danmoseley]

Is this a regression from 3.1?

[eiriktsarpalis]

I don't believe it is, the same behaviour reproduces in 3.1 as well.

[danmoseley]

OK, thanks just look on the lookout for regressions now we shipped (I'm adding the regression from last release label)