ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Nigel King <king@dircon.co.uk>
Subject: Re: Context Upgrade color problems
Date: Thu, 25 Jul 2002 10:25:58 +0100	[thread overview]
Message-ID: <B96582B6.93F2%king@dircon.co.uk> (raw)
In-Reply-To: <B96506E3.93D0%king@dircon.co.uk>

>> Does anybody have a procedure that they follow for an installation similar
>> to mine?
> 
> You could put the new context installation in a separate texmf dir which
> is searched before the old one. You can then go back to the old
> installation by removing or renaming the extra directory.
> Tetex is by default set up to search for files in $HOME/texmf before
> looking in the system-wide texmf directories. So, if you don't use this
> directory by now, you could take this location. Alternatively, define
> another one in texmf.cnf.
> 
I have now upgraded using a procedure similar to the one suggested by
Eckhart. I will publish the steps I have taken to do this later but a
problem that has emerged is a greater fussiness with colors. Previously I
could specify \red near the end

\setupcolors[state=start]
\starttext
This is \red red
\stoptext

doesn't work

\setupcolors[state=start]
\starttext
This is {\red red}
\stoptext

does work

Of more concern is that

\setupcolors[state=start]
\setuphead
    [section]
    [style={\ss\tfc\blue}]
\starttext
\section{introduction}
abc
\stoptext

or

\setupcolors[state=start]
\setuphead
    [section]
    [style=\ss\tfc\blue]
\starttext
\section{introduction}
abc
\stoptext

do not work the second version used to work with the November 2001 release.
How do I now get a colored section head?

(I hope this is not because I have made an error in the upgrade)

TIA
-- 
Nigel


       reply	other threads:[~2002-07-25  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B96506E3.93D0%king@dircon.co.uk>
2002-07-25  9:25 ` Nigel King [this message]
2002-07-25 10:14   ` Hans Hagen
2002-07-25 10:58     ` Nigel King

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=B96582B6.93F2%king@dircon.co.uk \
    --to=king@dircon.co.uk \
    /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).