If the marked region ends at the start of a line, do not include that
line in the indenting/undenting or commenting/uncommenting.  This is
closer to what the eye would expect.

Unset the "Modified" marker only at the point where the file was last
saved -- if there is such a point, because it can be missing when the
undo stack was discarded.

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

.
Reported-by: Liu Hao <lh_mouse@126.com>
Original-idea-by: Brand Huntsman <alpha@qzx.com>

When doing that, there is no need to save and restore the Modified
state when writing a marked region.

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

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

The escape sequence "Esc [ Z" is a backtab on most supported terminals,
so make sure convert_sequence() treats it as such.

The function get_keycode() should never return zero -- it should
return either the code from ncurses or the given fallback code.

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

To achieve that, fake the Shift key being held when indenting/
unindenting/commenting/uncommenting.
Reported-by: Brand Huntsman <alpha@qzx.com>

When the mark is on, instead of letting a <Tab> simply insert a Tab
character at the cursor position, let it indent the marked region.
Original-idea-by: Chris Allegretta <chrisa@asty.org>

Reference: http://php.net/manual/en/language.variables.basics.php



Also color keywords differently from strings.
Signed-off-by: Michael Francis <mikefrancis95@gmail.com>

Make both preceding character moves include the terminating byte.

The character move has already copied the terminating byte.
And a reallocation to save just one character of memory is
a waste of time.

And increase the contrast for the reminders, both for PO and Python.

A list of keywords can be obtained from `keyword.kwlist`.
Signed-off-by: Benjamin Mintz <bmintz@protonmail.com>

And also allow it when lines are only partially indented.

This makes it possible to equalize the indentations of (accidentally)
unevenly indented lines: by first fully unindenting a group of lines,
and then reindenting them to the desired amount.
Suggested-by: Liu Hao <lh_mouse@126.com>

Bright white on yellow stands out much more than grey on yellow.
Signed-off-by: Liu Hao <lh_mouse@126.com>

In this way we can delete things on the current line with ^K (after
Shift-selecting some text) without nano misdetecting a line change,

This fully fixes https://savannah.gnu.org/bugs/?52576.

Only when the cursor has moved off of the currrent line do we stop
prepending wrapped words to the next line.

This partially fixes https://savannah.gnu.org/bugs/?52576.

The option now causes nano to trim trailing whitespace also when
hardwrapping occurs while the user is typing.

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

To get rid of two double negatives.

It's better to color some invalid things as if valid than the other
way around.  So, as strings can validly contain any number of double
quotes, just accept *anything* between the delimiting double quotes
and demand that the closing quote is followed by whitespace or EOL.

The call of do_delete() four lines earlier already does a renumber.

When the WAS_FINAL_LINE flag is relevant (when NO_NEWLINES isn't set),
the only way for 'current' to be equal to 'filebot' is when 'current_x'
is zero.

This addresses https://savannah.gnu.org/bugs/?52546

.
Reported-by: Marius Schamschula <mschamschula@gmail.com>

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

When some or all edits have been undone, and the user starts to make
new edits, the old part of the undo stack is discarded, but this does
not mean that the undo stack doesn't go back to the very beginning.

This really fixes https://savannah.gnu.org/bugs/?52504.

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