Must I really understand from your reply that \setupinmargin[x=y] is not equivalent to \setupinmargin[][x=y]? That is: an absent optional argument is not really optionally absent? I checked by running the thing, of course, and the answer I found is "yes". The empty [] does not honor what leaving [] out does. To me -- but that is of course a personal opinion-- this is a little bit shocking. The fact that empty optional (supposed to leave the defaults as is) has another meaning than leaving out completely (which I also tend to interprete as leaving defaults untouched). May I ask for some thought about this behaviour? If it confuses me, I am vain enough to suppose others could be confused too. But thanks anyway for your elucidation. Hans van der Meer On 24 mrt 2010, at 15:21, Wolfgang Schuster wrote:
Am 23.03.10 22:36, schrieb Hans van der Meer:
I tried this code with both \setupinmargin[left][...] and \setupinmargin[][...]. The first one worked, the second obviously not. I take it therefore that the [left]-argument is mandatory. When the first argument is optional you can write
\setupinmargin[style=xxx,color=yy]
where the values are applied to all margin commands if not specified otherwise for a certain (e.g. \inleft) comand.
With the two argument version
\setupinmargin[left][style=xx,color=yy]
you can set special settings for the leftmargin texts, the global settings are now replaced.
The manual mentions you can use all commands from \framed but this is only true when you use the two argument version of the \setupinmargin command.
Wolfgang
___________________________________________________________________________________ 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 ___________________________________________________________________________________