Hi Hans,
here are a few questions which I want to ask since a few days.
1. texdefinition
I like start/stoptexdefinition because it makes the source for certain
macros more readable
than \def allows me but is there a way to use it for macros without
parameters?
2. commalists
Together with texdefinition I use now start/stopprocesscommalist
(feature request: I need also
start/stopprocessassignmentlist) but I can use the list value without
the need to define a command
where I specify what should happen with it
\startprocesscommalist[a,b,c,...]
the current list value is #1\par
\stopprocesscommalist
but why is there not something equivalent for the normal
processcommalist because the start/stop
method is not the best method when you need nested lists, something
like this would be nice then
(I know \doprocesscommalist is already defined):
\doprocesscommalist[a,b,c,...]%
{\processcommalist[x,y,z,...]%
{do something with #1 and ##1}}
3. setups
The various start/stopsetups environments another nice feature but
what's the correct method when
I want my own setup environment, should I adapt the following line
from core-env to my own command
\def\startsetups {\xxstartsetups\plusone \stopsetups } \let
\stopsetups \relax
and use method from lxml-ini to access/flush the content?
4. Mixed assignment/comma lists
Are mixed lists of normal comma elements and assignments are allowed
by ConTeXt’s syntax because
there is a command in the source (\processassignlist) to process the
non assignment values from
the list? On the other side these values generate a error message on
the terminal where one can read
there is a missing '=' in the element and this message can't be
disabled (without hacks).
Kind regards,
Wolfgang
_______________________________________________
dev-context mailing list
[email protected]
http://www.ntg.nl/mailman/listinfo/dev-context
