From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange behavior with TikZ
Date: Sat, 7 Oct 2017 08:40:13 -0400 (EDT) [thread overview]
Message-ID: <alpine.OSX.2.03.1710070838120.2759@zptvyy.pn> (raw)
In-Reply-To: <CACyK-epGmrai0W7DxfJAN1PT4fO+Ur+ioDBVKiLS0-Zisg+RXQ@mail.gmail.com>
On Sat, 7 Oct 2017, Fabrice Couvreur wrote:
> Hi Hans
> Sorry to insist, but I need to correct this anomaly for my documents that I
> give to students. If I compile with Context Standalone, it does not work,
> but maybe I do not do what you are suggesting :
I can confirm that color leakage. It happens due to pgfplots (and not
tikz). Here is the smallest example I could come up with that shows the
color leakage (the text is also colored magenta).
\usemodule[pgfplots]
\setuphead
[section]
[color=magenta]
\starttext
\startsection[title={Test}]
\startplacefigure[location={none,right}]
\hbox{\starttikzpicture
\startaxis
[
xmax=3, xmin=-3,
ymax=4, ymin=-5,
]
\stopaxis
\stoptikzpicture}
\stopplacefigure
\input knuth
\stopsection
\stoptext
Aditya
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-10-07 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 17:26 Fabrice Couvreur
2017-10-05 20:35 ` Hans Hagen
2017-10-05 20:51 ` Fabrice Couvreur
2017-10-07 10:17 ` Fabrice Couvreur
2017-10-07 12:40 ` Aditya Mahajan [this message]
2017-10-07 12:44 ` Aditya Mahajan
2017-10-07 13:59 ` Hans Hagen
2017-10-07 21:48 ` Fabrice Couvreur
2017-10-10 7:03 ` luigi scarso
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=alpine.OSX.2.03.1710070838120.2759@zptvyy.pn \
--to=adityam@umich.edu \
--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).