Up/down arrows with multiline input should not always recall history

[lzybkr]

When the current input has multiple lines, up/down arrow should be smart and not recall history if it makes sense to move the cursor instead (e.g. if the cursor isn't where we'd expect when cycling through history, then move up/down lines instead.)

[SmithCator]

Hello.
I also implemented PSConsoleHostReadLine for GUI-like keybindings.
PowerShell team made a fantastic function!
But I feel this function is incompatible with TabExpansion2 function, since PSConsoleHostReadLine requests fixed format text. So it is hard to modify output format of TabExpansion2.

btw, I prevented this issue by replacing keybinding for 'recall history'. ( recall history: Ctrl+Up/Down, cursor Up/Down: Up/Don )

http://gallery.technet.microsoft.com/scriptcenter/WindowsKeyBinding-for-60fb0d55

Stopgap!!!

[lzybkr]

I don't think PSConsoleHostReadLine and TabExpansion2 are incompatible, but implementing PSConsoleHostReadLine does require work to support tab expansion. If you call the correct API (which PSReadline does), TabExpansion2 will get called from the PowerShell engine, if it didn't, I'd certainly notice because my TabExpansion++ module (also on GitHub) wouldn't get called.

PSReadline is extensible enough so you can replace the key bindings for history recall, but the out of box experience must be as familiar as possible or people will be reluctant to start using it.

I opened this item because I have some ideas that should result it a mostly natural experience without learning new key bindings.