> I am trying to implement adequate syntax highlighting of an unsupported > language in Geany. It is a language with C-like syntax. To do this, I myself > created a configuration file according to the instructions.
Well, its better to actually state what you are trying to do when asking for help, and the answer is basically what I gave above, custom filetypes (as you clearly understand from the `styling=C` setting) are based on an existing filetype. Custom filetypes cannot change the code used by the existing filetype, and so are limited to the extent of any flexibility built into the existing filetype. Some filetypes are not flexible at all, and they are not required to be. They were written to address a particular language and cannot reasonably be expected to anticipate future uses (some may say abuses :). Note that the `keyword` list only applys to the highlighting lexers, the symbol parsers ignore that list since they have no idea what the keywords mean. The symbol parsers must parse the actual language for symbol definitions (such as the typedef you show in C above) they will likely be even less flexible than the highlighting lexers are since they need to know semantics (ie that `typedef` defines types). As I noted on the previous post, C is only required to accept identifiers using the portable character set (basically ASCII) and the symbol parser for C only recognises identifiers using those characters. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2504#issuecomment-628402893
