On Tue, 7 Dec 2010, Peter Münster wrote:

> On Mon, Dec 06 2010, Renaud AUBIN wrote:
>>
>> Concerning the color abstraction patch, one needs just to overload
>> Ccomment, Cpreproc, Cstring, Ctype, Ckeyword, Cname and Cfuncnbound to
>> use custom color scheme.
>
> You don't need that. There is already a standard interface for color and style
> configuration. Example:
>
> \setupstartstop[CSnippetComment][color=blue]
>
> So you can simplify t-pretty-c.mkiv:
>
> \unprotect
>
> \setupcolor[ema]
>
> \definestartstop
>    [CSnippetName]
>    [\c!color=darkgoldenrod,
>     \c!style=]

I have not looked into the new verbatim code yet, but I have been thinking 
about a similar interface for a new module that uses external programs for 
syntax highlighting (sort of a superset of t-vim that will allow one to 
use other programs like pgyments, etc.).

Why are you using a C prefix for all environments? Isn't it better to use 
a syntax like this:

\startsetups[verbatim:C]
\definestartstop[SnippetName][color=...,style=...]
\definestartstop[string][color=...,style=...]
....
\stopsetups

and then pass setups=verbatim:C to an appropriate \setup... command. That 
will make it easy to share the same syntax highlighting between different 
languages.

Aditya