From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Strange behavior with TikZ
Date: Sat, 7 Oct 2017 15:59:50 +0200 [thread overview]
Message-ID: <6f25e5aa-7cdc-da23-f3b7-b5cd07720aa9@wxs.nl> (raw)
In-Reply-To: <alpine.OSX.2.03.1710070842050.2759@zptvyy.pn>
On 10/7/2017 2:44 PM, Aditya Mahajan wrote:
> On Sat, 7 Oct 2017, Aditya Mahajan wrote:
>
>> 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).
>
> I use tikz/pgfplots extensively and started wondering why I don't see
> this error. Then I realized that I use a modified definition of
> starttikzpicture in my code:
>
> \define\starttikzpicture
> {\hbox\bgroup\forcecolorhack\tikzpicture}
>
> \define\stoptikzpicture
> {\endtikzpicture\egroup}
>
>
> With this definition, you code works correctly.
yes, i thought that was already done so someone needs to get that into
the official code base
(btw, it seems that there is also a \stopmodule done without
\startmodule when tikz is loaded)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-10-07 13:59 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
2017-10-07 12:44 ` Aditya Mahajan
2017-10-07 13:59 ` Hans Hagen [this message]
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=6f25e5aa-7cdc-da23-f3b7-b5cd07720aa9@wxs.nl \
--to=pragma@wxs.nl \
--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).