Thanks, the setting of `lexer_filetype=C` is crucial. I thought it is optional, as the documentation says: _the lexer you wish to use_ :)
Now my *.fe file get C coloring but I still cant get my own coloring. When I set: ``` [named_colors] myblue=#4682B4 myorange=#D2691E mybrown=#8B4513 [styling=C] comment=myblue;;false;true commentline=myblue;;false;true primary=myorange;;false;false secondary=mybrown;;false;false [keywords] primary=vertices edges faces constraint secondary=formula energy [settings] lexer_filetype=C ``` The comments are properly styled in "myblue" but the words in keyword lists `primary` and `secondary` are ignored. I can't figure out the philosophy behind the coloring in geany. For example, the only keywords lists in `filetypes.c` are `primary` `secondary` and `docComment` but C syntax coloring concerns not only words in these list but also other keywords like: operators (:*-=) or string constants in ".." etc. Where they are defined ? Here is what I can get easliy in [xnedit](https://github.com/unixwork/xnedit) (its coloring is based on regexp):  but now I need a simple IDE for systems other than Linux... -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/4292#discussioncomment-12968111 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/repo-discussions/4292/comments/12968...@github.com>
