544351f3be
syntaxes: replace [[:space:]] with [[:blank:]] to exclude carriage return
...
In many places a carriage return is not valid whitespace and should
thus not be colored as such. In some of these places a vertical tab
or form feed is maybe valid whitespace, but it would be ugly or even
wrong to color them because they are not part of the subsequent
comment or keyword.
This fixes https://savannah.gnu.org/bugs/?60456 .
2021-04-27 11:18:41 +02:00
208146f2f2
syntax: go: add author and license line
...
In the original submission (https://savannah.gnu.org/patch/?8189 )
the submitter said: "I hereby put it into the public domain."
Public-domain license: https://directory.fsf.org/wiki/License:CC0
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
2020-12-10 15:48:28 +01:00
3480518a5c
syntax: go: highlight the chan keyword, and the special +build comment
...
This fixes https://savannah.gnu.org/bugs/?58424
Reported-by: Ryan Westlund <rlwestlund@gmail.com>
Signed-off-by: Ryan Westlund <rlwestlund@gmail.com>
2020-05-26 16:50:31 +02:00
fea5d7c612
syntaxes: uniformize the initial comment
2020-04-20 19:21:56 +02:00
302ea79d1c
syntaxes: put the 'linter' and 'formatter' commands on a separate line
...
To show that they are a different class of thing than the file-matching
regexes and the comment thing, which all kind of "describe" the file.
2019-11-04 20:56:41 +02:00
4281b6becb
commands: rename 'fixer' to 'formatter', to be less misleading
...
The word "fixer" sounds too much as if the command would be able
to fix mistakes or correct errors. Especially when seen next to
"linter", it sounds as if one does a syntax check and the other
fixes the found mistakes. (Although the command might in theory
be used for this, it is not its intended purpose.)
2019-10-25 17:24:28 +02:00
8749ccb469
syntax: nanorc: colorize the 'fixer' command as valid
...
Also add a default formatting command to the Go syntax.
2019-10-14 10:28:45 +02:00
2d434f63e2
syntaxes: remove all traces of the 'formatter' command
2018-08-09 21:12:10 +02: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
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
b0ef2e2803
build: move the syntax files out of the doc/ directory
...
They are not documentation, they are functional elements of nano.
2016-12-30 22:05:01 +01:00
Benno Schulenberg