From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: colors for pretty-printing (was: Re: pret-c.lua -> v-c.lua)
Date: Tue, 7 Dec 2010 08:29:47 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1012070822330.20575@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20101207112502.GA10103@micropit.couberia.bzh>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1299 bytes --]
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
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-07 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 8:17 pret-c.lua -> v-c.lua Peter Münster
2010-12-03 9:28 ` Renaud AUBIN
2010-12-03 21:31 ` Peter Münster
2010-12-03 21:38 ` Hans Hagen
2010-12-04 2:31 ` Renaud AUBIN
2010-12-05 2:06 ` Renaud AUBIN
2010-12-05 9:36 ` Peter Münster
2010-12-05 19:20 ` Renaud AUBIN
2010-12-06 8:54 ` Hans Hagen
2010-12-06 14:04 ` Peter Münster
2010-12-06 19:55 ` Renaud AUBIN
2010-12-07 11:25 ` colors for pretty-printing (was: Re: pret-c.lua -> v-c.lua) Peter Münster
2010-12-07 13:29 ` Aditya Mahajan [this message]
2010-12-07 13:48 ` colors for pretty-printing Hans Hagen
2010-12-07 17:57 ` Aditya Mahajan
2010-12-07 19:30 ` Hans Hagen
2010-12-08 5:22 ` Aditya Mahajan
2010-12-07 20:35 ` Renaud AUBIN
2010-12-07 21:45 ` Peter Münster
2010-12-08 20:13 ` Renaud AUBIN
2010-12-10 10:47 ` Peter Münster
2010-12-10 10:54 ` Renaud AUBIN
2010-12-10 11:11 ` Peter Münster
2010-12-10 11:28 ` Renaud AUBIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.01.1012070822330.20575@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).