From: Hans Hagen <pragma@wxs.nl>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: colors without \definecolor
Date: Mon, 08 Feb 2010 13:28:53 +0100 [thread overview]
Message-ID: <4B700385.20400@wxs.nl> (raw)
In-Reply-To: <4B6FD17D.60401@googlemail.com>
On 8-2-2010 9:55, Wolfgang Schuster wrote:
> Am 08.02.10 09:40, schrieb Hans Hagen:
>
>>> D’oh. I looked in the source and missed this but I wonder
>>> if this had been always the case because the manuals
>>> {and the wiki) mention only \color[name]{...}.
>>
>> all commands that use \groupedcommand have that property
>
> But used \color always \groupedcommand or was this added later and the
> original definition was what is mentioned in the manual (\color[]{})?
it's a very old command so it might not have used groupedcommand in the past
also, at the time of manual writing no groupedcommand like things were
there anyway
but .. there's another reason ...
\color{...} does not grab an argument but does some aftergroup trickery
so it might not work in all cases
also in mkii we inject literals and we could end up with dangling revert
color cases being nodes that could interfere somehow
mkiv is more robust
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 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
___________________________________________________________________________________
prev parent reply other threads:[~2010-02-08 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 20:41 Philipp Gesang
2010-02-05 7:31 ` Wolfgang Schuster
2010-02-05 14:49 ` Philipp Gesang
2010-02-06 7:55 ` Wolfgang Schuster
2010-02-07 6:24 ` Aditya Mahajan
2010-02-07 21:56 ` Wolfgang Schuster
2010-02-08 8:19 ` Mojca Miklavec
2010-02-08 8:51 ` Wolfgang Schuster
2010-02-08 8:40 ` Hans Hagen
2010-02-08 8:55 ` Wolfgang Schuster
2010-02-08 12:28 ` Hans Hagen [this message]
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=4B700385.20400@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.com \
/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).