670dd9bbe0
tweaks: condense two regexes in the Tcl syntax, and add a comment
...
Also, make a range of characters more explicit.
2018-12-17 16:00:54 +01:00
9cdc64c97a
syntax: tcl: colorize comments normally, not with a background hue
...
This makes for a less "messy" and more readable appearance.
Suggested-by: Michael Siegel <msi@malbolge.net>
2018-12-17 15:35:56 +01:00
5acfa5bb7b
tweaks: slightly indent warnings and errors during the configure phase
...
To make them stand out in the waterfall of messages.
2018-12-16 14:41:31 +01:00
e938c24d04
tweaks: renumber a couple of symbols, and reshuffle a bit of code
...
Also, contract the regex for key strings.
2018-11-07 19:30:04 +01:00
f55a3fabef
input: recognize some escape sequences for <Shift+Delete>
...
Also, hard-bind <Shift+Delete> in the same way as <Backspace>.
This fixes https://savannah.gnu.org/bugs/?54948 ,
and fixes https://savannah.gnu.org/bugs/?54975 .
2018-11-07 19:17:16 +01:00
ae3ec1784d
options: add --zap, that makes <Bsp> and <Del> erase a marked region
...
Using --zap or -Z on the command line, or 'set zap' in a nanorc file,
makes the <Bsp> and <Del> keys erase selected text (a marked region)
as they do in some other editors, and without affecting the cutbuffer.
This fulfills https://savannah.gnu.org/bugs/?54837 .
Requested-by: Liu Hao <lh_mouse@126.com>
Signed-off-by: Brand Huntsman <alpha@qzx.com>
2018-11-04 11:46:57 +01:00
02eaa4ce6d
tweaks: fold a few pairs of regexes into each other
2018-11-03 21:32:07 +01:00
636e9ac3e8
syntaxes: remove several redundant end-of-line anchors from regexes
2018-11-03 21:12:44 +01:00
af71d44e4e
tweaks: snip trailing whitespace that ended with a non-breaking space
2018-11-03 20:41:42 +01:00
5f1b618a5a
syntax: nanohelp: properly color the keystroke "Sh-^Del"
...
This fixes https://savannah.gnu.org/bugs/?54758 .
2018-09-30 20:40:20 +02:00
790f98560b
syntax: python: do not highlight 'print' and 'exec' in Python 3
...
Assume that 'print' and 'exec' are statements when they are followed
by whitespace, and are functions otherwise. This does not highlight
"print'x'" nor "print{x}", but these statements are poor style.
Signed-off-by: Benjamin Mintz <bmintz@protonmail.com>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
2018-09-20 20:45:01 +02:00
e2051a61e0
syntax: sh: let the header regex match also busybox shell scripts
...
And recognize calls via 'env' too.
This addresses https://savannah.gnu.org/bugs/?54674 .
Reported-by: Aaron Sears <geodelic@gmail.com>
2018-09-18 19:06:11 +02:00
921f8ae4c9
syntax: default: colorize also two-digit and capitalized nano versions
2018-08-30 19:46:34 +02:00
bf5949395d
syntax: lua: do not color strings inside comments, and add a linter
...
Also, don't partially color "..." as an operator, because it isn't,
and color also the unary operator "#".
Signed-off-by: Mark-Weston <markweston@cock.li>
2018-08-28 20:16:16 +02:00
c524fbe6d0
tweaks: remove some ineffectual parts from header-line regexes
...
Adding "[abc]*" does not restrict the recognized header line in any way.
Also, improve the header-line regex for shell scripts, because it should
not match "barunscript" (for example).
2018-08-28 19:53:36 +02:00
850e538ff7
syntax: python: avoid coloring the three special values inside strings
...
Reported-by: Benjamin Mintz <bmintz@protonmail.com>
Suggested-by: Brand Huntsman <alpha@qzx.com>
2018-08-16 19:56:01 +02:00
18419b5e3f
syntax: awk: recognize any {g,m,n,}awk script also by its shebang line
...
This fulfills https://savannah.gnu.org/bugs/?54516 .
Suggested-by: Javier Valencia <javiervalencia80@gmail.com>
2018-08-15 20:20:22 +02:00
2d434f63e2
syntaxes: remove all traces of the 'formatter' command
2018-08-09 21:12:10 +02:00
db1893ef2d
syntax: nanorc: recognize 'yesno' as a valid menu to bind/unbind keys in
2018-08-06 18:05:10 +02:00
ac102a7516
tweaks: show "Space" and "Bsp" in the help text of the browser
...
These keys make more mnemonic sense for scrolling than F7 and F8.
Also adjust the nanohelp syntax to cover the lone word "Space".
2018-07-31 20:36:32 +02:00
4a268678a5
syntax: sh: recognize more file extensions and header lines
...
Signed-off-by: Devin Hussey <husseydevin@gmail.com>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
2018-07-20 19:12:20 +02:00
acadf71b13
syntax: nanorc: show ^@ as validly rebindable, but not any ^digit
2018-07-11 14:14:40 +02:00
8492de53f7
syntax: makefile: color all keywords that GNU make recognizes
...
Plus one that automake recognizes: if. Color them only at the start
of a line. Also color all possible assignment sequences (surrounded
by spaces to not color the ones in shell fragments), and add some
comments.
2018-05-30 11:29:08 +02:00
22663f8a2e
syntax: makefile: recognize also an all-lowercase makefile name
...
Recognize not just "Makefile" but also "makefile" and "GNUmakefile".
And recognize these only when they are the full filenames, not when
they are the tail part of a longer name.
Signed-off-by: Cristian Caloghera <cristi.caloghera@gmail.com>
2018-05-22 20:41:43 +02:00
cdd637d69f
syntaxes: condense and/or correct some extension regexes
2018-05-18 20:40:08 +02:00
858663444e
new feature: an option to make the 'nextword' function stop at word ends
...
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>
2018-05-10 11:32:01 +02:00
30a984661b
syntax: po: highlight also other escaped characters, not just \n
...
Especially color \a and \t, to make it easier to distinguish them
from contiguous text.
2018-04-17 09:56:19 +02:00
cf1129a8b4
syntax: sh: colorize options only when they are preceded by whitespace
...
To prevent any filenames containing hyphens getting partially colored.
Reported-by: Brand Huntsman <alpha@qzx.com>
2018-03-30 10:46:56 +02:00
0bce5ba4d9
syntax: sh: color options distinctively, and color also long options
...
Also add some comments, and accept hyphens in function names.
2018-03-29 09:51:39 +02:00
20d1823d90
syntax: sh: uncolor "tar" when it's part of a filename
2018-03-28 14:04:00 +02:00
e01bcddf16
docs: document the newly added color name "normal"
2018-03-28 14:03:52 +02:00
1de3667555
syntax: sh: color also the 'cut', 'head', 'tail', and 'sort' commands
2018-03-27 14:09:38 +02:00
ae9ec6d4ad
syntax: nanorc: color also bindings to a string as valid
2018-03-01 10:09:28 +01:00
8f1a657a37
bindings: revert the ^/ changes, as ^/ is not always Go-To-Line
...
On a Linux console, ^/ produces Backspace, making it unrebindable.
This fixes https://savannah.gnu.org/bugs/?53248 .
2018-03-01 09:50:54 +01:00
082e5db4b7
syntax: color also ^/ in nano's help texts and in nanorc files
...
As of commit c79fe1a1
2018-02-27 18:06:33 +01:00
b027263a37
small addition: allow customizing the color of an error message
...
The new option 'set errorcolor' allows the user to specify the color
combination for the status bar when an error message is displayed.
2018-02-23 12:35:17 +01:00
fef195bce9
syntax: go: highlight also floats with leading zeroes as valid
...
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>
2018-02-20 10:31:38 +01:00
3e1fc6385b
syntaxes: remove quotes from each syntax name, and color it differently
...
The different color will make the name stand out, as it should, instead
of looking the same as all the regex strings.
2018-02-14 17:36:50 +01:00
452008c81d
syntax: go: colorize only valid octal numbers
...
Reported-by: Tom Levy <tomlevy93@gmail.com>
2018-01-26 11:15:26 +01:00
8067efa6cc
syntax: nanohelp: color also the Sh-Tab key combo
2018-01-09 16:34:31 +01:00
c6f367268b
syntax: lua: do not color debug.setinfo as it doesn't exist
...
Reported-by: Tom Levy <tomlevy93@gmail.com>
2018-01-06 17:59:28 +01:00
5965e80a38
tweaks: fold some regexes into one another, for conciseness
...
The anchored "^texture" appears to have been a mistake.
Inspired-by: Tom Levy <tomlevy93@gmail.com>
2018-01-01 16:00:18 +01:00
a794c3318b
syntax: go: sign of exponent in number literal is optional
...
Signed-off-by: Tom Levy <tomlevy93@gmail.com>
2018-01-01 15:27:31 +01:00
d04b0c123e
syntax: go: fix word boundary before dot in number literal
...
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>
2018-01-01 15:25:26 +01:00
21cd953e85
syntax: lua: condense some regexes, tweak comments, reorder things
...
Also remove some redundant backslashes and parentheses.
2018-01-01 14:59:00 +01:00
058b9da9b9
syntax: lua: add new and missing standard library functions
...
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>
2018-01-01 14:35:19 +01:00
38a10a62d0
syntax: lua: support fractional part and exponent for decimal and hex
...
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>
2018-01-01 14:15:14 +01:00
091e8faf6d
syntax: lua: require at least one digit for hexadecimal numbers
...
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>
2018-01-01 13:51:10 +01:00
1f48ed0412
syntaxes: remove redundant word-boundary markers
2017-12-30 17:32:15 +01:00
4f2b01c7e5
syntax: lua: correct the word boundaries on standard library functions
...
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>
2017-12-28 21:46:26 +01:00
Benno Schulenberg