Also, swap the logic around, to use less braces.

There is no need for a counter, nor an old counter to compare it with.

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

(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>

Reported-by: Sumedh Pendurkar <sumedh.pendurkar@gmail.com>

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/?49058 reported by Rishabh Dave.

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

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

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

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

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 avoids showing a ghost item in, for example, the WriteOut menu
when not using --tempfile and the user does not bind 'discardbuffer'.

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 http://savannah.gnu.org/bugs/?48698

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

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

Saving roughly twenty microseconds at startup.

Also, when a key string does not denote a Ctrl nor Meta nor Function key,
there is no point in assigning a keycode, because plain characters cannot
be used as a function shortcut.

The keycode is not a sequence; it is a single integer value.

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

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

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.