It will be reallocated soon enough when the size increases again.

Also remove an unneeded nulling.

The verbosity "hid" the really relevant information:
filename, line number, and the error message.

Valid values and other details can be found in the manual pages.

When the palette is getting initialized, it is too late to send any
error messages about the rcfile options to standard error.

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

.
Reported-by: Brand Huntsman <alpha@qzx.com>
Signed-off-by: Brand Huntsman <alpha@qzx.com>

When we're just searching, we do want to report the occurrence at
the cursor (after coming full circle) as a match, so that we can
mention that this is the only occurrence.  When replacing, we do
not want to replace this match twice.

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

Suggested-by: Brand Huntsman <alpha@qzx.com>

So the result could be used during RC-file reading.

Also drop an old debugging fragment.

There shouldn't be two separate variables (but with the same name) that
count the number of digits seen.  Fuse them into a single static var.

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

Use the same method as in parse_verbatim_kbinput() for Unicode input.

Also, when replacing forwards, do not first skip the occurrence at the
cursor and then replace it at the end of the cycle, but begin with it,
as one would expect.

This fixes https://savannah.gnu.org/bugs/?52789
and fixes https://savannah.gnu.org/bugs/?52791.

These three functions are needed only when both linter and speller
are available.

This fixes https://savannah.gnu.org/bugs/?52834.
Reported-by: <akiko@mailbox.org>

If help is enabled, those functions should be described too,
and if nanorc is enabled, they should both be rebindable.

Each leading tab is converted to two tabs, and any leading four spaces
is converted to one tab.  The intended tab size (for keeping most lines
within 80 columns) is now four.

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

.
Reported-by: Brand Huntsman <alpha@qzx.com>

When unindenting/uncommenting affected the bottom line of the marked
region, keep affecting this line also during subsequent consecutive
indenting/commenting.

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

So that Commenting comes closer to the somewhat related Indenting
and Unindenting functions.

Also, make the descriptions for indenting/unindenting more precise.

So they will be found quicker.

Also fold two assignments into one.

They were mistakenly added by changeset fb85c055, four commits ago.