This avoids a bunch of warnings when compiled with -pedantic:

	ISO C forbids comparison of ‘void *’ with function pointer

Commit 0cf455bc introduced the typo.

Exclude the confusing, pleonastic 'sc' abbreviation from their names.

The new option 'set errorcolor' allows the user to specify the color
combination for the status bar when an error message is displayed.

And when configured with --enable-tiny --enable-nanorc.

The different color will make the name stand out, as it should, instead
of looking the same as all the regex strings.

This addresses https://savannah.gnu.org/bugs/?48992.

In this way a single keystroke can produce a fragment of text or a
series of commands, or a mix of the two.  It is like a prerecorded
macro.

This fulfills https://savannah.gnu.org/bugs/?52931.

And one for me, for the much changed keyboard stuff.

And rewrap some lines, three of them to make them equal to another.

At that point, ptr will necessarily point at EOL -- *ptr == '\0'.

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>

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.

The option now causes nano to trim trailing whitespace also when
hardwrapping occurs while the user is typing.

Also, remove an unneeded pair of braces.

Signed-off-by: Marco Diego Aurélio Mesquita <marcodiegomesquita@gmail.com>

When not finding a .nanorc file in the user's home directory, nano will
look for a nanorc file in $XDG_CONFIG_HOME and in the ~/.config/nano/
fallback directory.  And when not finding a .nano/ subdir in the user's
home directory, nano will look for (or create) the history files in
$XDG_DATA_HOME or in the ~/.local/share/nano/ fallback directory.

This is a partial implementation of the XDG Base Directory Specification:
https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html

,
for the purpose of reducing the clutter in a user's home directory, and
to make it easier to back up just the configuration files.
Signed-off-by: Simon Ochsenreither <simon@ochsenreither.de>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>

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

If the user uses a single version of nano, they have no need for
--quiet.  If they do sometimes use an older version and don't want
to see the warnings, they can use 2>/dev/null (they could make an
alias for that and put it before the call of nano).

The user told nano to start, thus nano should *start* -- without
halting and without nagging the user.