And refer backward instead of forward.

In nano, -a is only effective when also -$ is given, so this will
not conflict with Pico since Pico does not know the -$ option.

Extend get_softwrap_breakpoint() to break softwrapped lines on
whitespace when a flag is set.  This flag is controlled by the new
rcfile option "atblanks".  The '>' characters marking two-column
characters at the edge of the screen are disabled when it's on.

If get_softwrap_breakpoint() can't find whitespace in screen range, it
will break the line on the screen edge.  (In this case, a blank can be
on the last column of the screen, but text can't, so that a blank on the
last column doesn't become invisible and possibly break the display.)

This fulfills https://savannah.gnu.org/bugs/index.php?49959

.
Requested-by: Nicholas Boel <axxisd@gmail.com>

Also remove the backslashes from the two syntaxes that contained them.

This completes the fix for https://savannah.gnu.org/bugs/?51370.

For the man page, encode them properly, and for the Info stuff,
just set the right document encoding.

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

The comment marker is not «."» but «.\"», which requires three
backslashes to specify.  Also adjust the documentation.

Also, use proper mark-up for the examples.

The dash doesn't have to be the first non-option argument: it can
be anywhere among the filenames -- there can even be multiple ones
(but don't mention this explicitly).

Especially: get rid of the "Up: (dir)" link that points nowhere.

Also, add a horizontal line before the final Table of Contents.

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

Also, harmonize some configure-option descriptions,
add a slash after a subdir, and fix a typo.

Also, add two missing configure options, and frob some other things.

And make the strings after "start=" and  "end=" more readable.

Mention some things that really set nano apart from Pico.
Plus some other small tweaks here and there.

Furthermore, change an item header into a question, swap two items,
and tweak the formatting a bit.

The interval 2013-2017 for the Free Software Foundation is valid
because in those years there were releases with changes by either
Chris or David, and the GNU maintainers guide advises to mention
a new year in all files of a package, not just in the ones that
actually changed, and be done with it for the rest of the year.

Mention the ability to use <Tab> in the search history, the ability
to restore the cursor position when reopening a file, the ability to
read output of a command, and the lack of file-managing commands in
the file browser.

And slightly change the existing one for normal users.

And modify a few wordings too.

This addresses a followup of https://savannah.gnu.org/bugs/?50362

.
Reported-by: Mike Frysinger <vapier@gentoo.org>

Also, add two cross references: one in words, and one with a link.