On Jan 4, 2005, at 20:59, Eric Hsu wrote:
[...] if Bundle writers could agree on a reasonable base set and rename their names, that could go a long way towards making the colors customizable before Allan gets his next solution done.
Also for the next solution this will be required. At least to have colors apply to multiple files. The idea is that for a given color a CSS-like selector is given to describe which elements should have this color. So that could be “Comments, 'C++ Comments'” or “HTML > PHP Comments" (the first would match all elements Comments or 'C++ Comments' where the latter would match all Comments in HTML-embedded PHP).
Allan may have to set standards like this anyway, unless he writes a small GUI Syntax File browser that displays the Names with a little Color Picker patch. That would be fabulous, of course.
Actually, I did/do consider having each bundle/syntax include an example source that uses all matched language constructs. The user would then just click a portion of this example (showed by TM) and TM would tell the name/path of the construct to which the user could associate styles/settings.