The fsfromline() function is mostly used by the undo functions, which
are not present in the tiny version.  It is also used by the comment/
uncomment feature, but this feature cannot be enabled when --enable-tiny
is in effect.

Instead compute directly whether we're at a softwrapped part or not.

Convert digits() to take a ssize_t instead of an int, since it's
used on ssize_t line numbers.  And properly use the long modifier
when displaying a line number.

Also, conditionalize the digits() prototype.

(The variable 'pletion_line' is not conditionalized with this option, as
it would become messy.  The compiler will probably be able to elide it.)

When using --enable-tiny, it is not possible to use --enable-wordcomp,
because the word completion function uses the undo system.

Executing the 'complete_a_word' function will search from the start
of the current buffer for entire words that begin with the fragment
that is before the cursor, and will complete this fragment to the
first word that is found.  Each consecutive call of 'complete_a_word'
will search for the next matching word and will complete the fragment
to that.  By default the function is bound to the ^] keystroke.
Signed-off-by: Sumedh Pendurkar <sumedh.pendurkar@gmail.com>
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>

None of the prompts offer a total-refresh shortcut -- only the
edit window, the help viewer, and the file browser provide this.

Achieve this by reusing the code that gives feedback when trying to
save a buffer while using --tempfile and the file has no name yet.

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

Achieve this elegantly by factoring out the reading of one rcfile.

Also remove some unneeded prototypes, adjust some comments, and
move a constant definition to the top of the file.

This make tiny nano slightly less tiny, but makes the code more readable.

It does not update anything -- it just picks a new point from
where to start displaying the buffer.  All actual updating of
the screen is done by edit_refresh() and edit_redraw() and such.

It can be activated with --linenumbers on the command line or with
'set linenumbers' in a nanorc file, and it can be toggled with M-#.
Signed-off-by: Faissal Bensefia <faissaloo@gmail.com>
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>

Instead of figuring them out from the string.  This is possible
because those dedicated editing keys cannot be rebound anyway.

This fixes https://savannah.gnu.org/bugs/?49099,
and fixes the unreported corresponding bugs for
<End> and <Del> and typing extra characters.

And also case-sensitive searches, backward searches, and searching again.

Mentioning "GNU nano" instead of "This program" and referring to the
website instead of to a postal address.

Leave the optimization of actual screen writes to ncurses.

Add the keycodes and routines to allow the user to forego setting the
mark explicitly (with M-A / ^6) and instead quickly select a few words
or lines by holding down Shift together with the movement keys.

(Some combinations with Shift are swallowed by some terminal emulators.
To work around some of those, the combinations Shift+Alt+Left/Right work
as Shift+Home/End and Shift+Alt+Up/Down work as Shift+PageUp/PageDown.)

This fixes https://savannah.gnu.org/bugs/?48751 reported by Andrew Ho.

This also fixes compilation when configured with --enable-tiny.

If this breaks your build, please send report or instructions or patch.

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

Straightforward code is more important than the tiniest possible binary.

Also adjust some comments and rename a variable.

For horizontal scrolling, it is not the /desired/ column position that
is relevant for determining whether a line needs to be redrawn after a
cursor movement, but the /actual/ column positions before and after.

This fixes https://savannah.gnu.org/bugs/?48627,
and fixes https://savannah.gnu.org/bugs/?48629.

Having two unneeded parameters in the tiny version is acceptable --
the code gets so much more readable.

Leave the rest of any escape sequence to be processed normally, which
should be possible because those characters are all in ASCII range.

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

There is no need to specially flag a function key or editing key --
the keycode is indication enough in itself: outside of byte range.

And instead of using two key types, just use a bool to indicate whether
a keystroke involves Meta.

A keycode is either already in byte range (so there is nothing to do)
or it is not and it shouldn't be (so there is nothing to do either).

After initialization, the type of a key is never used nor needed
(other than for meta keys).

Those lines don't exist in that mode -- the relevant subwindows are
smaller, or have been made smaller just before.

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

And hard-bind the keys Ctrl+Up and Ctrl+Down to these functions.

Unlike the paragraph-jumping code, these new functions disregard
any indentation, treating only blank lines as separators.  They
also do an automatic smart home when that option is set.

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