ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: ntg-context@ntg.nl
Subject: Re: ppchtex color
Date: Wed, 13 May 2009 10:55:15 +0200	[thread overview]
Message-ID: <200905131055.15194.alan.braslau@cea.fr> (raw)
In-Reply-To: <4A0A85CE.9050501@wxs.nl>

On Wednesday 13 May 2009 10:33:18 Hans Hagen wrote:
> Alan BRASLAU wrote:
> > Works correctly (bonds in red, atoms in black):
> >
> > \usemodule[chemic]
> > \setupchemical[rulecolor=red]
> > \starttext
> > \startchemical
> > 	\chemical[ONE,SB,Z0][C]
> > \stopchemical
> > \stoptext
> >
> >
> > However, the following variant does not work.
> >
> > \usemodule[chemic]
> > \starttext
> > \startchemical[rulecolor=red]
> > 	\chemical[ONE,SB,Z0][C]
> > \stopchemical
> > \stoptext
> >
> > I don't understand, as my (quick) look at the source code
> > indicates that the parameters should be handled identically.
>
> no, that was actually the problem ... local vs global ... for the moment
> set it up local (per formula) as i need to make an inheritance chain
>
> now that i've split in mkii/mkiv that's easier since we no longer have
> to keep things working in latex (which means that we can use more core
> helper code)
>
> just remind me occasionally

OK. The following extension would also be useful:

\usemodule[chemic]
\starttext
\startchemical
	\chemical[SIX,B,rulecolor=red,AU][]
\stopchemical
\stoptext

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-05-13  8:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  9:22 The ultimate (?) float problem Piotr Kopszak
2009-05-12 10:02 ` Hans Hagen
2009-05-12 10:16   ` Piotr Kopszak
2009-05-12 10:44     ` Hans Hagen
2009-05-12 10:28 ` luigi scarso
2009-05-12 11:28   ` Piotr Kopszak
2009-05-12 11:46     ` luigi scarso
2009-05-12 13:03       ` Piotr Kopszak
2009-05-12 13:11         ` luigi scarso
2009-05-12 13:18           ` Piotr Kopszak
2009-05-12 13:32             ` Wolfgang Schuster
2009-05-12 13:45               ` Piotr Kopszak
2009-05-12 14:16               ` luigi scarso
2009-05-14  9:17                 ` Piotr Kopszak
2009-05-12 13:29       ` ppchtex color Alan BRASLAU
2009-05-12 17:57         ` Hans Hagen
2009-05-12 18:07         ` Hans Hagen
2009-05-12 18:17         ` Hans Hagen
2009-05-12 20:45         ` Hans Hagen
2009-05-12 21:30         ` Alan BRASLAU
2009-05-12 21:53           ` Hans Hagen
2009-05-12 21:51         ` Alan BRASLAU
2009-05-13  8:33           ` Hans Hagen
2009-05-13  8:55             ` Alan BRASLAU [this message]
2009-05-13 11:25               ` Hans Hagen

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=200905131055.15194.alan.braslau@cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.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).