/usr/share/nano/js.nanorc configuration: syntax highlighting

Question

I have a question regarding syntax highlighting with JavaScript using nano. I have tweaked the js.nanorc file to my liking using the colors I prefer:
## New updated taken from [url]http://wiki.linuxhelp.net/index.php/Nano_Syntax_Highlighting[/url]
syntax "JavaScript" "\.(js)$"
## Default
color brightgreen "^.+$"
## Decimal, cotal and hexadecimal numbers
color brightyellow "\<[-+]?([1-9][0-9]*|0[0-7]*|0x[0-9a-fA-F]+)([uU][lL]?|[lL][uU]?)?\>"
## Floating point number with at least one digit before decimal point
color brightyellow "\<[-+]?([0-9]+\.[0-9]*|[0-9]*\.[0-9]+)([EePp][+-]?[0-9]+)?[fFlL]?"
color brightyellow "\<[-+]?([0-9]+[EePp][+-]?[0-9]+)[fFlL]?"
## Keywords
color brightcyan "\<(break|case|catch|continue|default|delete|do|else|finally)\>"
color brightcyan "\<(for|function|if|in|instanceof|new|null|return|switch)\>"
color brightcyan "\<(switch|this|throw|try|typeof|undefined|var|void|while|with)\>"
## Type specifiers
color brightmagenta "\<(Array|Boolean|Date|Enumerator|Error|Function|Math)\>"
color brightmagenta "\<(Number|Object|RegExp|String)\>"
color brightmagenta "\<(true|false)\>"
## String
color brightblue "L?\"(\\"|[^"])*\""
color brightblue "L?'(\'|[^'])*'"
## Escapes
color red "\\[0-7][0-7]?[0-7]?|\\x[0-9a-fA-F]+|\\[bfnrt'"\?\\]"
## Comments
color brightwhite start="/\*" end="\*/"
color brightwhite "//.*$"
However, I would also like the rendering to be a little different. For example:
var code = function(nano) {
console.log("I would like these parenthesis to be a different color than the keywords");
The parenthesis and keywords(var, function, for, while....etc) are the same color, how can I adjust the rendering so that the parenthesis or brackets will be a different color?
Last edited by rg_arc (2012-04-04 13:40:31)

Answer 1

doug piston wrote:I deal with alot of .mk files and would love to see it there.
You mean GNU makefiles?
I'm afraid they might be out of scope for this generic config-file syntax.
Logically they're not system config files, and technically they're a pretty specialized and complex format (different "types" of rules, rules spanning multiple lines, rules containing arbitrary Bash code, etc.).
This is how an .mk file currently looks with this highlighting syntax:
$ nano -Y conf /usr/lib/httpd/build/rules.mk
And apart from highlighting variables of the form $$abc or $(abc), I'm not sure how much can be improved here without breaking the highlighting for more conventional config files.
It would probably be better to create a specialized highlighting syntax just for .mk files.
EDIT: I sat down and did just that, here's the result: nano syntax highlighting: GNU makefiles, and here is how the above makefile snipped looks with it:
Last edited by sas (2012-02-01 15:18:52)