ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Lmtx + pgfplots compilation error
Date: Tue, 7 Apr 2020 14:20:50 +1200	[thread overview]
Message-ID: <20200407022050.vzk5vpvcnmvicmz3@worklaptop> (raw)
In-Reply-To: <CACyK-epASjPrsKv23yX6Uv2k3rMJMAAGxvcVD73-OAp1zHMFUg@mail.gmail.com>

The problem is that pgfplots uses the ^^ syntax to access characters but
this relies on ^ having catcode 7 which is not the case by default in
ConTeXt.  I had a similar issue in PGF before and that was fixed by just
replacing the ^^ syntax with the ascii code constants from
syst-ini.mkxl.

Cheers, Henri

On 06/04/20, 22:23, Fabrice Couvreur wrote:
> Hi,
> Still with the idea of using lmtx, I get a compilation error when I use
> pgfplots.
> Thank you.
> Fabrice
> ####################################################
> open source     > level 9, order 92, name 'pgfplotsbinary.data.code.tex'
> 
> tex error       > tex error on line 42 in file
> pgfplotsbinary.data.code.tex: ! Undefined control sequence
> 
> l.42 \catcode`\ =11^^I\expandafter\xdef\csname pgfp@bin@
> 
> \the\counter^^I\endcsname{^^20}\endgroup\advance\counter by1
> lua error:
> 
> ?
> 
> 
> 
> <empty file>
> 
> 
> The control sequence at the end of the top line of your error message was
> never
> \def'ed. You can just continue as I'll forget about whatever was undefined.
> 
> 
> mtx-context     | fatal error: return code: 256
> 
> TeX Output exited abnormally with code 1 at Mon Apr  6 22:19:01

> ___________________________________________________________________________________
> 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
___________________________________________________________________________________

  reply	other threads:[~2020-04-07  2:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 20:23 Fabrice Couvreur
2020-04-07  2:20 ` Henri Menke [this message]
2020-04-07 12:22   ` Fabrice Couvreur
2020-04-08  9:20     ` Henri Menke
2020-04-08  9:52       ` Fabrice Couvreur
2020-04-08 10:40         ` Henri Menke
2020-04-08 21:40           ` Fabrice Couvreur
2020-04-08 22:02             ` Aditya Mahajan
2020-04-08 22:07               ` Aditya Mahajan
2020-04-13  9:41                 ` Fabrice Couvreur
2020-04-13 10:12                   ` Aditya Mahajan
2020-04-13 21:58                     ` Fabrice Couvreur

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=20200407022050.vzk5vpvcnmvicmz3@worklaptop \
    --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).