Creating a colorscheme

[EllKyGr]

Hello!

Recently started using and customizing Micro, adding some plugins and then try several color schemes. Although some are decent looking they lack depth. So I've been tweaking with "darcula" in particular to address most of the keywords in Python, type words, variables and so on. However while doing so several of the commands do not work. I might missing something so any help would be useful, these are some of the commands that, at least for me, don't work properly:

• Both True and False keep the constant base color
  color-link constant.bool
  color-link constant.bool.true
  color-link constant.bool.false

• Just like a normal string, hover just shows the underline
  color-link constant.string.url

• Nothing seem to change with these two
  color-link identifier.class
  color-link type.keyword

Also the identifier only works with the built-in functions, not the custom ones (which retain the default color, this also applies with the function preceded by the dot operand), and some functions are considered "type" like enumerate, range, and so on.
Also, is it possible to make internal parentheses change color if they're inside another pair? Currently curly braces remain the same color as the string even if it is a f-string and the expression inside also stays the same.
I tried to use the yaml method but it raised an error and I didn't understand how to fix it (haven't user a yaml file before) so for now I'm trying this method.

Thanks in advance!

[Andriamanitra]

I've been tweaking with "darcula" in particular to address most of the keywords in Python, type words, variables and so on. However while doing so several of the commands do not work. I might missing something so any help would be useful, these are some of the commands that, at least for me, don't work properly

This is determined by the syntax file for Python. Anything you use in a colorscheme only works with languages that have syntax files that define those tokens. For example if you look at the Python syntax file you can see True and False are both defined as simply "constant" (and not "constant.bool.true" like they are in some others like the toml syntax file). You may add customized versions of the syntax files under ~/.config/micro/syntax/ to make them work better with your colorscheme.

Also, is it possible to make internal parentheses change color if they're inside another pair? Currently curly braces remain the same color as the string even if it is a f-string and the expression inside also stays the same.

Not really. You might be able to hack together something that sort of works by abusing regions rules of the syntax files, but micro's syntax highlighting system is not really advanced enough to do this kind of thing properly.

[EllKyGr]

I see. I added the syntax file for Python to the syntax directory. After running Micro again this error raises:
Error parsing syntax file python3: interface conversion: interface {} is nil, not []interface {}

[Andriamanitra]

That error is due to #3458 making syntax files incompatible with older versions of micro (see #3538 (comment)).

To fix it you can either update micro, or add rules: [] back into the regions in the syntax file (you can look at git history to see how the syntax file used to be before #3458).

[EllKyGr]

I uninstall then reinstall it again with the getmic.ro and got the 2.0.14 version. Again got the same error, added rules: [] to python3.yaml file and now it works. Does the nightly version works without adding the rules?

[Andriamanitra]

Yes, the fix should be present in the nightly release, or you could build micro from source. There has not yet been a stable release since the change.

[EllKyGr]

Fair enough. It works as intended now, I'll keep on with my tweaking. Thanks for the guidance!