From: Jorge Manuel <desdechaves@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Install Tikz in LMTX tree
Date: Wed, 11 Mar 2020 17:35:26 +0000 [thread overview]
Message-ID: <B5DBC087-1CA4-4D27-9532-F7DE3B2F17CF@gmail.com> (raw)
In-Reply-To: <0f8668ae-b917-5034-d03d-16bc1380590d@xs4all.nl>
Thanks to Hans Hagen.
\newcount\eTeXversion \eTeXversion = 2000
\newcount\eTeXrevision \eTeXrevision = 0020
In the top of my tex file fixed the problem.
Jorge
> On 10 Mar 2020, at 14:06, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> On 3/10/2020 11:32 AM, Henri Menke wrote:
>
>> There are still people trying to run TikZ on plain TeX with the Knuth
>> engine: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920368
>
> hm, so you can't actually use etex goodies unless you emulate them
>
>>> \newcount\eTeXversion \eTeXversion = 2000
>>> \newcount\eTeXrevision \eTeXrevision = 0020
>> Hm, I need something that *all* eTeX engines provide that I can check.
>> And these seem to have met that requirement. I really don't want to
>> write a huge cascade of if-s to test for different engines.
>
> I'll add dummies then but be aware that you actually should test for the primitives that you expect because I'm not even sure if luatex bumped the number. As you mention "all" it means that you expect differences because "all" implies differences here. What if someone runs a very old (experimental) etex.
>
> (\scantokens, \readline, \detokenize, \savingvdiscards are likely to be untouched .. it depends on what primitives you expect to use)
>
>
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2020-03-11 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 21:59 Jorge Manuel
2020-03-10 9:01 ` Hans Hagen
2020-03-10 10:32 ` Henri Menke
2020-03-10 14:06 ` Hans Hagen
2020-03-11 17:35 ` Jorge Manuel [this message]
2020-03-11 19:23 ` 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=B5DBC087-1CA4-4D27-9532-F7DE3B2F17CF@gmail.com \
--to=desdechaves@gmail.com \
--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).