When 'afterends' is set and Ctrl+Right or Shift+Ctrl+Right is pressed,
nano will stop at the ends of words instead of their beginnings.
Signed-off-by: Mark-Weston <markweston@cock.li>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>

Especially color \a and \t, to make it easier to distinguish them
from contiguous text.

To prevent any filenames containing hyphens getting partially colored.
Reported-by: Brand Huntsman <alpha@qzx.com>

Also add some comments, and accept hyphens in function names.

On a Linux console, ^/ produces Backspace, making it unrebindable.

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

As of commit c79fe1a1, the more readable ^/ has replaced ^_ as the
advertised shortcut for Go-To-Line -- color it too as valid.

The new option 'set errorcolor' allows the user to specify the color
combination for the status bar when an error message is displayed.

See the discussion on the mailing list:
https://lists.gnu.org/archive/html/nano-devel/2018-01/msg00022.html
https://lists.gnu.org/archive/html/nano-devel/2018-02/msg00090.html

Signed-off-by: Tom Levy <tomlevy93@gmail.com>

The different color will make the name stand out, as it should, instead
of looking the same as all the regex strings.

Reported-by: Tom Levy <tomlevy93@gmail.com>

Reported-by: Tom Levy <tomlevy93@gmail.com>

The anchored "^texture" appears to have been a mistake.
Inspired-by: Tom Levy <tomlevy93@gmail.com>

Signed-off-by: Tom Levy <tomlevy93@gmail.com>

The fragment "\<\." can never match anything because \< matches the
beginning of a word but "." is not a word character.

Replace \< with \B (the empty string not at the edge of a word).
Signed-off-by: Tom Levy <tomlevy93@gmail.com>

Also remove some redundant backslashes and parentheses.

The list now includes all the Lua 5.3 functions listed on
https://www.lua.org/manual/5.3/#index

.

Also, remove the coloring of just the library name, so that
only known library functions get highlighted.
Signed-off-by: Tom Levy <tomlevy93@gmail.com>

As of Lua 5.2: "Hexadecimal constants also accept an optional fractional
part plus an optional binary exponent, marked by a letter 'p' or 'P'"
(see at the end of https://www.lua.org/manual/5.2/manual.html#3.1).

The new regexes do not match a leading nor a trailing dot, but they
are good enough.  Discussion on the mailing list:
https://lists.gnu.org/archive/html/nano-devel/2017-12/msg00121.html

Signed-off-by: Tom Levy <tomlevy93@gmail.com>

Since a "0x" by itself is invalid.  Also add word boundaries, so that
e.g. "00x1" (which is invalid) does not get partial highlighting.

Also remove some redundant backslashes from the strings regex.
Signed-off-by: Tom Levy <tomlevy93@gmail.com>

Functions such as "io.close" should only be highlighted when the
package name ("io") is a word by itself, otherwise code such as
"fooio.close" gets unexpected partial highlighting.
Signed-off-by: Tom Levy <tomlevy93@gmail.com>

Also, remove angle-bracketed "strings" -- they don't exist.

Also, remove the coloring of special single-quoted strings as they
get recolored by the subsequent general string-coloring command.

And remove the coloring of all-uppercase words, as other editors
do not color those either.

Either by whitespace or by the start of a line.

This avoids treating part of a URL as a comment.

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



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

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>

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

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

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.

Since file-5.10 (end of 2011), libmagic identifies a C file in most
cases as "C source" instead of as "C program".  Nano's magic strings
for some other files didn't match any more what file-5.32 currently
produces, either.  So, they have been adjusted, new ones added, and
old ones deleted.

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

Requested-by: Brand Huntsman <alpha@qzx.com>