This fixes https://savannah.gnu.org/bugs/?47710
and fixes https://savannah.gnu.org/bugs/?49088.

Returning a zero would mean returning a ^Space -- the keycode that
by default is bound to the Next-Word function.  So, unbinding the
keys to which the modified Arrow keys are hard bound would cause
the latter ones to mysteriously jump to the next word.

This partially fixes https://savannah.gnu.org/bugs/?49058.

This fixes https://savannah.gnu.org/bugs/index.php?42189.

And also case-sensitive searches, backward searches, and searching again.

And correct a comment: the key /does/ occur also in the tiny version.

These keycodes have non-rebindable entries in the list of shortcuts, so
they will always be there -- no need for a function call to find them.

In the tiny version it would beep and report an unbound key for every
window resize.

Mentioning "GNU nano" instead of "This program" and referring to the
website instead of to a postal address.

Add the keycodes and routines to allow the user to forego setting the
mark explicitly (with M-A / ^6) and instead quickly select a few words
or lines by holding down Shift together with the movement keys.

(Some combinations with Shift are swallowed by some terminal emulators.
To work around some of those, the combinations Shift+Alt+Left/Right work
as Shift+Home/End and Shift+Alt+Up/Down work as Shift+PageUp/PageDown.)

And move a statement to a better place.

This also prevents the message from spilling into the help lines
when the terminal is less than four columns wide.  (Not that one
can read anything then, but it looks better.)

This fixes https://savannah.gnu.org/bugs/?48787.

This fixes https://savannah.gnu.org/bugs/?48520.

This fixes https://savannah.gnu.org/bugs/?48751 reported by Andrew Ho.

This also fixes compilation when configured with --enable-tiny.

If this breaks your build, please send report or instructions or patch.

This fixes https://savannah.gnu.org/bugs/?48711.

(It may have been necessary in the past; there is no need for it now.)

This fixes https://savannah.gnu.org/bugs/?48633.

For horizontal scrolling, it is not the /desired/ column position that
is relevant for determining whether a line needs to be redrawn after a
cursor movement, but the /actual/ column positions before and after.

This fixes https://savannah.gnu.org/bugs/?48627,
and fixes https://savannah.gnu.org/bugs/?48629.

Leave the rest of any escape sequence to be processed normally, which
should be possible because those characters are all in ASCII range.

This fixes https://savannah.gnu.org/bugs/?48318.

These codes are the basic codes that get assigned for the movement keys
in the list of shortcuts -- they don't need any translation.

Again, just for preapring an easier return from the parsing routine.

There is no need to specially flag a function key or editing key --
the keycode is indication enough in itself: outside of byte range.

The keycode is not a sequence; it is a single integer value.

And instead of using two key types, just use a bool to indicate whether
a keystroke involves Meta.

A keycode is either already in byte range (so there is nothing to do)
or it is not and it shouldn't be (so there is nothing to do either).

After initialization, the type of a key is never used nor needed
(other than for meta keys).