RFC: Add history_move_{next/prevoius}

[azat]

Right now there is UP/DOWN arrows, that is binded to
history_prevous/history_next accordingly.

But in case of multiline history entry it will navigate through the
lines in the current history itemfirst, and this may not be the requird
behavior.

So now replxx will have history_move_*, that will always navigate
through history, regardless of new lines in query.

New history_move_{next/prev} binded to M-UP/M-DOWN (like in readline).

[AmokHuginnsson]

It is good idea regarding unconditional history move up/down actions availability to the user.
Regarding default key binding for CTRL-p/CTRL-n, there is already a pinned issue about exactly that.
I will investigate if using Meta-Up/Meta-Down is a viable option.

[azat]

Regarding default key binding for CTRL-p/CTRL-n, there is already a pinned issue about exactly that.

#78

I will investigate if using Meta-Up/Meta-Down is a viable option.

Thanks.

You mean Meta-Up/Meta-Down for history_move_{next/previous}?
I can convert the patch to use Meta-Up/Meta-Down for new bindings for now (I can change default bindings anyway).

So you don't like to change C-p/C-n behavior in general?

[azat]

I can convert the patch to use Meta-Up/Meta-Down for new bindings for now (I can change default bindings anyway).

Done.

[AmokHuginnsson]

Hi.

I have amended you PR by changing action names.
I also added regression tests.
It is pushed to master now.

Thank you for this contribution!

[AmokHuginnsson]

I forgot to answer your question.
I am very hesitant to change default that were present in the library from the beginning.
Some users could be accustom to it already.
The original defaults did not come from readline but from tcsh shell I was using at the time...