Done and committed on
http://gitorious.org/c-pretty-printer-module-for-context-mark-iv
> In your t-pretty-c.mkiv you can use \setupcolor[ema] without problems.
___
If your question is of interest to others as well, plea
On Fri, Dec 10 2010, Renaud AUBIN wrote:
> Ok but then why did you define a specific color palet?
>
> local function color_init()
> color = 0
> local def_colors = -- \setupcolor[ema] introduces new line...
The comment says it: \setupcolor[ema] introduces new line and that's annoying
when
Ok but then why did you define a specific color palet?
local function color_init()
color = 0
local def_colors = -- \setupcolor[ema] introduces new line...
"\\definecolor [darkred] [r=.545098]" ..
"\\definecolor [orchid][r=.854902,g=.439216,b=.839216]" ..
On Wed, Dec 08 2010, Renaud AUBIN wrote:
> In fact, I just need to find unique names for my colors to not overload
> the existing ones…
\doifcolorelse{new funny color}
{Error: funny color already exists!}
{\definecolor[new funny color][...]}
With \setupcolor[ema] or \
I need to not redefine.
Quoting Hans: "maybe you should protect the color names as for instance
redefining darkred might not be the intention"
In fact, I just need to find unique names for my colors to not overload
the existing ones…
Renaud
> I still don't understand. Where do you need to redef
On Tue, Dec 7, 2010 at 2:30 PM, Hans Hagen wrote:
> On 7-12-2010 6:57, Aditya Mahajan wrote:
>
>> Thanks for the explanation. But, I am not too keen to write parsers on
>> my own when I can easily borrow existing ones.
>
> sure, but a simple one can be:
>
> function myparser(str)
> .. call your p
On Tue, Dec 07 2010, Renaud AUBIN wrote:
>
> > So you can simplify t-pretty-c.mkiv:
> >
> > \unprotect
> >
> > \setupcolor[ema]
> >
> > \definestartstop
> > [CSnippetName]
> > [\c!color=darkgoldenrod,
> > \c!style=]
> >
> > and so on...
> >
> OK, but anyway, I have to protect the c
> 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=darkgol
On 7-12-2010 6:57, Aditya Mahajan wrote:
Thanks for the explanation. But, I am not too keen to write parsers on
my own when I can easily borrow existing ones.
sure, but a simple one can be:
function myparser(str)
.. call your prog do do something with str and return the result
end
But it
On Tue, 7 Dec 2010, Hans Hagen wrote:
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 Cfuncnb
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 d
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 standar
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
config
13 matches
Mail list logo
