GitLab

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

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

The $ sign looks too much like an S, and it "obscures" the answer by
being so "massive".  The < and > signs are lighter and work better.

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

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

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

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

And move a statement to a better place.

This also prevents the message from spilling into the help lines
when the terminal is less than four columns wide.  (Not that one
can read anything then, but it looks better.)

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

Even when the edit window consists of just one or two lines, the PageUp
and PageDown functions (^Y and ^V) should continue to move the window.

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

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

That is: don't try to look at open files when none are open yet.

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

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

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

When using the default speller or the formatter, the placewewant is
remembered.  So it should be remembered too when the user specifies
a different speller.

(This behavior was inadvertently lost last year, in commit 82d737ee.)

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

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

Instead be more specific and say that the directory is not writable.

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

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

It is quicker to do a handful of superfluous compares at the end of
each line than it is to compute and keep track of and compare the
remaining line length the whole time.

The typical line is some sixty characters long, the typical search
string ten characters -- with a shorter search string the speedup is
even higher: some fifteen percent.  Only when the string is longer
than half the average line length does searching become slower with
this new method.

All this for a UTF-8 locale.  For a C locale it makes no difference.

Now that mbstrncasecmp() does the right thing, there is no need any
more to verify that only a valid multibyte sequence was matched.

(See https://savannah.gnu.org/bugs/?45579 for a test case.)

Also, this will make it possible to search for invalid sequences.

(Currently it isn't possible to enter a search string with invalid
characters, but... a user might edit the search history file.  And
if pasting at the prompt is implemented, it will be trivial to enter
invalid sequences if you have a file that contains them.)

Persisting might lead to count 'n' reaching zero, which would mean that
the needle has matched, which is wrong when one of the strings contains
an invalid or incomplete multibyte sequence.

That is: don't run towlower() on the two differing bytes when having
reached the end of one of the strings.

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

In the bargain, don't do the conversion to lowercase twice.

Furthermore, persist when encountering invalid byte sequences --
until finding bytes that differ.