fix: lua highlighting to match styleguide

[jack-mil]

Again, the Npp language syntax lexer is very basic, so this results in a much less colorful theme then VSCode (esp. in doc-comments)

Before	After
Idea for doc-comments (?)

Another example

VS Code for reference

To be merged after #14

Relates to #17

[sgoudham]

I think I'd prefer doc comments to be overlay even if it looks more "bland", the yellow is quite off-putting to me.

[uncenter]

I think I'd prefer doc comments to be overlay even if it looks more "bland", the yellow is quite off-putting to me.

(This is how we do it in all the other syntax highlighting ports fwiw.)

---

Can we make booleans peach instead of mauve here?

[jack-mil]

Can we make booleans peach instead of mauve here?

Not really, all builtin keywords are hardcoded for this one, and it includes "true" "false" and "nill" along with "function" "return" "local" etc....
So unless you are ok with all of those being peach too...

[uncenter]

It's fine then, keywords being mauve is more important than bools being peach. 👍

[jack-mil]

Sorry to wake this conversation up again, but I realized when looking at this again that to be consistent with choices in the other PRs, I think braces and parenthesis should be overlay2. In Npp this is the "OPERATOR" group for Lua, so unfortunately that means [+-*/=] won't be sky. This is the same compromise for Python in #31.