There are actions that relate to editing the input too, which I also want to
test, but I'm not minded to lump them all in the same file. So here I'm
renaming to make it clear these tests are just about movement. The editing
ones will come next in their own file.
This is just getting a feel for how I'll go about testing these. The main
focus here won't be on the bindings themselves -- they're not really
interesting and I feel could change over time anyway as people's tastes
settle down. What I want to test here are the actions that get bound.
This is just an initial small set of what's going to be a much bigger
collection of Input action tests.
I'm going to be adding more tests for Input, and I don't want to be doing
one large monolithic file of them, so this makes a space where
Input-targeting tests can live together and be easy to spot.
This makes no difference to anything; but I think grouping the bindings into
similar groups will make it easier for folk to read and find things.
See #1310.
This makes no difference to anything; but I think it makes for code that's
easier on the eye so someone scanning down the list of bindings will see the
more descriptive key first.
See #1310.
And in doing so bind it to Ctrl+U (readline-common). Right now I'm not aware
of a common combo for this on Windows, but we can add a binding for this if
one becomes apparent.
See #1310.
And in doing so bind it to Ctrl+K (macOS/Emacs/readline-common). Right now
I'm not aware of a common combo for this on Windows, but we can add a
binding for this if one becomes apparent.
See #1310.
