I studied jEdit's highlighting definition syntax and figured out that this is not limited by the highlighting system, but by the number of token types.
I've tried jEdit long time ago, then it was quite user unfriendly, crashing and run slowly on my then computer. Now I've found that with plugins, it has all features I look for to switch from my favorite but old editor, HomeSite (which's developement has already ended), EXCEPT for the genial syntax coloring of HomeSite... I will put a screenshot at http://ondra.zizka.cz/temp/HomeSite_screenshot.png . (Intentionally synthetized mix of all languages together, what is bad practice).
So, my feature request is:
As far as the "parsing" system is capable of the feature I ask for, and even the mode files would not have to be rewritten, I guess this is only a matter of the following:
Let's not have fixed set of token types; instead, let's track all token types of each mode and let it be configurable similarly to shortcuts:
1) Separate color configuration for each mode, and
2) Global default color config for certain token types (comment, keyword1, operator), which would be applied if the specific mode setting would be "use default for this token type".