Windows 10 WSL - arrow keys, Home and End not working

[benedikt90]

In reference to issue number 1588, I open this one as the issue is not actually resolved. After patching conemu, copy and pasting works, but the arrow key behaviour is broken (command completion).

To cite myself:

Up and down [arrows] go through history, but before doing this [(updating conemu)], when I wrote "ssh" it would only cycle through my previous ssh commands. Pos1 and End still don't seem to do anything... It's odd...
I'm on Win 10 Pro 1803 17134.81

[deadalnix]

Ok so as it turns out, the p flag used to default to value 5 for cur_console, but doesn't anymore. This is what was causing the issue in vim and alike for me. Replacing p to p5 in my templates solved it.

[mthsy]

Thanks. It works for me.

[benedikt90]

Perfect, this works!

For anyone wondering how to do it:
Goto Settings --> Startup --> Tasks
Now in all your "predefined tasks" that are used for WSL consoles, edit the command:
e.g. from %windir%\system32\bash.exe ~ -cur_console:p to %windir%\system32\bash.exe ~ -cur_console:p5 (note the p5 instead of p)

"Save Settings" and enjoy! :)

[isapir]

The solution #1832 (comment) from @reijin90 works, but sometimes I start with a regular shell and only then call

bash

How can I get the cursor keys to work then?

[WayneD]

Yeah, vim is very broken in normal WSL. It even blocks the typing of capital-letter commands (e.g. ZZ) and ctrl keys. I work around the issue by starting up a screen session, since vim works fine inside screen. You may need to define SCREENDIR to get screen to run, though, since there's a bug with the auto-creation of the default /run/screen dir (or you can add rules to create it with mode 1777).

[asuiu]

I have the same issue and -new_console:p5 fixed it for me.

[taichushouwang]

My cmder is the newest version, 1035, I also have the same issue, but I can't find "%windir%\system32\bash.exe ~ -cur_console:p" such this string, How can i do?