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

.
Reported-by: David Lawrence Ramsey <pooka109@gmail.com>

So the cursor won't be visible at the end of the status-bar message
while reading in a large file.

The code has been there for the last thirty releases -- for six
whole years -- more than enough time to have served its purpose.

The recent migration of the history routines forgot to add the new
file to the list of files from which strings should be extracted.

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

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

This kind of addresses https://savannah.gnu.org/bugs/?51685.

In atblanks mode, if a softwrapped chunk ends with a double-width space
character (say, Unicode 003000, Ideographic Space), and that would put
half of the character past the edge of the screen, break before it.

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

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

Or rather, to make searching for the PRESERVE option easier.

Simply redraw the browser screen upon every keystroke when --showcursor
is in effect, to be certain that the cursor will be placed again at the
correct spot.

This fixes https://savannah.gnu.org/bugs/?52078
and fixes https://savannah.gnu.org/bugs/?52079

.
Reported-by: David Lawrence Ramsey <pooka109@gmail.com>

The basic idea is that the cursor is always off, except when it needs
to be on: when waiting for text input, and in a few other cases: when
something was searched and found in the help viewer, and in the file
browser when option -g is in effect.

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

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

When reducing the search string to at most half the screen width,
it should employ its width in columns, not its length in bytes.

Also adjust the type of a variable.

This fixes http://savannah.gnu.org/bugs/?52057.

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

.
Reported-by: David Lawrence Ramsey <pooka109@gmail.com>

So that it is not a substring of some other name.

The functions to read and write history files will not even be called
when the home directory is missing, so there is no need to check for
that eventuality again.

When history has changed, not all three listst can be empty.

Populating the search, replace, and execute lists makes use of the
function update_history() which sets history_changed to TRUE, which
meant that the search_history file would always get written even if
nothing had changed.

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

This fixes http://savannah.gnu.org/bugs/?52042

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

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

When multiple files were open and [x/n] was being shown in the title
bar, don't show nano's name and version number when just one buffer
remains open, but show [1/1] instead.  It is less surprising.