Adjust to the changed meaning of 'whereis': it is no longer do_search()
but do_search_forward().
Hinted-at-by: Brand Huntsman <alpha@qzx.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>

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

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

So that these functions have bindings by default, and easy bindings.
Add them to the help viewer too, so that searching backward becomes
possible there.

This also fixes https://savannah.gnu.org/bugs/?51735

.
Reported-by: Urja Rannikko <urjaman@gmail.com>
Signed-off-by: Urja Rannikko <urjaman@gmail.com>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>

The edit subwindow will be completely redrawn twelve lines down,
and window_init() takes care of clearing the status bar.

Without them, nano still compiles for me, with everything enabled,
even when using --enable-debug, --enable-utf8, and --with-slang.

Also, allow Ctrl+Left/Right with --enable-tiny --enable-browser.

And hide the cursor again as soon as the user scrolls.
Achieve this through making the 'didfind' variable global.

Also, remove a superfluous call of wnoutrefresh(), as bottombars()
already does that.

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

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

Also, trim some comments and avoid an unused-variable warning.

Also, reshuffle two initializations to go sit with the other ones.

Things have morphed over time and display_buffer() no longer actually
displays the buffer -- it just displays the title bar, precalculates
the multiline color info, and schedules a refresh of the edit window.

Also, avoid an unused-variable warning when configured with
--enable-tiny --enable-help --enable-multibuffer.

We should measure the length of each /translated/ shortcut description,
not of the original English one.

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

Also, mention that help texts can now be searched through, update
a copyright notice, and update and simplify a copyright year.

And in the process transform the token DISABLE_HELP to ENABLE_HELP.

This avoids applying the default syntax, or the syntax specified
with --syntax, to a ^G help text.

And allow 'N' for searching the next occurrence.  Add the
same keystrokes to the file browser too, for consistency.

Since the help text is searchable, an <End> would go to the end of the
text but would leave a blank line above the statusbar -- a blank line
that wasn't there before, and that is not reached when simply holding
down <Down> all the way from the top.

So that the shortcut explanations get properly aligned.

When nano has multiple files open, closing a help buffer should
not switch to the next buffer in the ring but to the preceding one,
because it was from there that the help screen was invoked.

Also, save and restore all the flags in a single swoop.

There is no need to restore NOREAD_MODE after unsetting it, because
any files mentioned on the command line have already been /not/ read.

However, prefer moving the starting point of the text backwards over
moving it forward, so that of the same paragraph more text is shown
instead of less.  But scroll an empty line out of view -- no text is
"lost" then.

Allow the user to search in a help text with ^W and M-W.

Achieve this by not writing the help text directly to the screen
but first writing it to a temporary file and then opening this file
in a new buffer, and treating it specially: the normal file-reading
feedback is suppressed, the titlebar shows the headline of the text,
the cursor is hidden, and the menu is limited to just the up and down
movements and searching.

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

.
Signed-off-by: Rishabh Dave <rishabhddave@gmail.com>

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.

Verify at startup that the number is not too small.

"Q" is a pretty standard key to exit from something, and "X" is fairly
mnemonic -- better than "E" at least.