Repository navigation
Home key and End key are now not working with TERM=xterm #421
Description
Readline won't register proper key presses. They were confirmed working with the first System.Console patch. Something happened between the first System.Console patch and the dotnet cli build to cause them to stop working.
VSO create date - 12/22/2015 11:09:00
Activity
andyleejordan commentedon Jan 23, 2016
Certain terminal emulators send Home and End as multiple character combinations, which
Console.ReadKey()does not register as Home and End, and we're not currently checking for either.This is doable, but won't be fun.
andyleejordan commentedon Jan 28, 2016
This is related to #461.
andyleejordan commentedon Feb 19, 2016
This got stranger. It works correctly in Tmux (with
TERM=screen). Something aboutxtermin particular is sending a weird key combo for this.vors commentedon Feb 20, 2016
Can we support
Ctrl+AandCtrl+D?There are no separate Home and End on Mac:
Fn+Shift+LeftandFn+Shift+Rightworks (just found them, when I was writing it)Also, how about
Ctrl+C? It's so annoying not being able to drop a long lineandyleejordan commentedon Feb 20, 2016
Zach Folwick (@zach-folwick) Was wanting that in #562, but I think it falls under porting
PSReadLine. If that is ported and we have it by default, we'll get everything we want. Without having to implement it twice.Jason Shirk (@lzybkr) What do you think?
andyleejordan commentedon Feb 20, 2016
Ctrl-Cshould work. It's handled by PowerShell and used to interrupt the running cmdlet.vors commentedon Feb 20, 2016
Andy Jordan (@andschwa) yes, it works as an interrupt. But when I'm entering a command and say wrote a long line (without running it), I need a way to drop it.
andyleejordan commentedon Feb 20, 2016
Ah, like
ESC's behavior on Windows.vors commentedon Feb 20, 2016
Oh
Escworks, good to knowandyleejordan commentedon Feb 26, 2016
HOMEandENDwork properly underscreenandputtyTERMs.And
HOMEis coming in as^[[1~.So this is a case of
xtermnot being 100% correct for certain Terminal emulators, like PuTTY. And is likely the case on MobaXterm.A (@ealexjordan) Can you see what the
HOMEkey is coming in as in your emulator? (PressCtrl-V + HOME.) If it's the same, thenxtermis not correct for MobaXterm and we can close this.andyleejordan commentedon Feb 26, 2016
It appears to me that
TERM=screenis what MobaXterm should be using, as that makes HOME/END line up with the expected key codes.This is an emulator configuration issue, not a PowerShell or .NET issue.