From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Install Tikz in LMTX tree
Date: Tue, 10 Mar 2020 23:32:47 +1300 [thread overview]
Message-ID: <20200310103247.pn7agfrdngled566@laptop.local> (raw)
In-Reply-To: <906b923e-5e56-ef73-15ef-91ce2a97560a@xs4all.nl>
On 10/03/20, 10:01, Hans Hagen wrote:
> On 3/9/2020 10:59 PM, Jorge Manuel wrote:
>
> > \pgfutil@packageerror #1#2#3->\errhelp {#3}\errmessage {Package #1
> > Error: #2}
> > l.11 \pgfutil@packageerror{PGF}{PGF requires etex in extended mode}{}
> > %
> >
> > <empty file>
> >
> >
> > This error message was generated by an \errmessage command, so I can't
> > give any
> > explicit help. Pretend that you're Hercule Poirot: Examine all clues,
> > and deduce
> > the truth by order and method.
> >
> >
> > Anybody has a clue how to fix this?
> i'm surprised that there is (still) a check fot that because all tex's
> default to etex .. you can try to put this at the top of yuor file
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
>
> \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.
> afaik there has never been a formal etex version 1 (in use) and never a
> fundamental revision ... in lmtx we no longer have these versions (pdftex,
> etex, omega, aleph, etc) as they serve no purpose
>
> 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-10 10:32 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 [this message]
2020-03-10 14:06 ` Hans Hagen
2020-03-11 17:35 ` Jorge Manuel
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=20200310103247.pn7agfrdngled566@laptop.local \
--to=henrimenke@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).