On 7-12-2010 2:29, Aditya Mahajan wrote:
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:


So you can simplify t-pretty-c.mkiv:




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.).

it all boils down hooking in a parser then:

local function parser(s)
  local s = somexternalthing(s)
  -- feedback s

visualizers.register("myparser", { parser = parser })


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


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.

it's hard to come up with common names for characteristics for all those languages but at some point we can have a set predefined as default

btw, startstop can inherit (now):


etc so there is no need for setups

                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
If your question is of interest to others as well, please add an entry to the 

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net

Reply via email to