ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: groupedcommand with color
Date: Tue, 14 Feb 2012 13:37:21 +0100	[thread overview]
Message-ID: <5B102CA6-86A9-4033-88CE-E543B4D1F6DD@st.estfiles.de> (raw)
In-Reply-To: <4F3A51C6.8090006@wxs.nl>


Am 14.02.2012 um 13:21 schrieb Hans Hagen:

> On 14-2-2012 12:55, Steffen Wolfrum wrote:
>> Hi,
>> 
>> due to \color[]{} now needs an argument, groupedcommand doesn't work as before:
>> 
>> 
>> \define\PlainSwitch%
>> {\groupedcommand{\language[de]\ss}{}}
>> 
>> \define\ColorSwitch%
>> {\groupedcommand{\language[de]\ss\color[darkred]}{}}
>> 
>> \starttext
>> 
>> English: \date
>> 
>> {\PlainSwitch German \date}
>> 
>> English: \date
>> 
>> {\ColorSwitch German \date}
>> 
>> Test \date
>> 
>> \stoptext
>> 
>> Someone knows what to change here (in order to get the red "G" back)?
> 
> something
> 
> {\groupedcommand{\language[de]\ss\startcolor[darkred]}{\stopcolor}}


In version 2012.01.16  this gives an error:

! Extra }, or forgotten \endgroup.


Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-02-14 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 11:55 Steffen Wolfrum
2012-02-14 12:21 ` Hans Hagen
2012-02-14 12:37   ` Steffen Wolfrum [this message]
2012-02-14 12:44     ` Hans Hagen
2012-02-14 13:26       ` Steffen Wolfrum
2012-02-14 20:29         ` Wolfgang Schuster
2012-02-14 12:44     ` Philipp Gesang

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=5B102CA6-86A9-4033-88CE-E543B4D1F6DD@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).