ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: pgfplots broken?
Date: Tue, 04 Nov 2014 17:21:25 +0100	[thread overview]
Message-ID: <5458FD05.1070304@wxs.nl> (raw)
In-Reply-To: <CAHy-LL9cTz359auJ0=0WsQbNdat2DJUswn4sVvyinM4Zam8-qQ@mail.gmail.com>

On 11/4/2014 4:49 PM, Mikael P. Sundqvist wrote:

> ConTeXt$ find . -iname '*pgfluamath*'
> ./tex/texmf-modules/tex/generic/pgf/libraries/luamath/pgfluamath.parser.lua
> ./tex/texmf-modules/tex/generic/pgf/libraries/luamath/pgfluamath.functions.lua
> ./tex/texmf-modules/tex/generic/pgfplots/lua/pgfplotsoldpgfsupp_pgfluamath.parser.lua
> ./tex/texmf-modules/tex/generic/pgfplots/lua/pgfplotsoldpgfsupp_pgfluamath.functions.lua

require("foo.bar")

means: look for file [configured paths]/foo/bar.[so|dll|lua]

so, those filenames looks weird. I have no clue how e.g. latex or plain 
looks for files with require (maybe they kick in some kpse lookup) but 
i'm not going to add such an exception to context

local foo = dofile(resolvers.findfile(foo.bar.lua"))

might work for such files

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2014-11-04 16:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 11:42 Mikael P. Sundqvist
2014-11-04 12:58 ` luigi scarso
2014-11-04 15:35   ` Hans Hagen
2014-11-04 14:27 ` Keith J. Schultz
2014-11-04 15:32 ` Hans Hagen
2014-11-04 15:49   ` Mikael P. Sundqvist
2014-11-04 16:21     ` Hans Hagen [this message]
2014-11-05 11:22   ` Keith J. Schultz
2014-11-04 14:44 Akira Kakuto
2014-11-04 18:13 ` Mikael P. Sundqvist
2014-11-04 19:12   ` Hans Hagen
2014-11-04 19:22     ` Mikael P. Sundqvist
2014-11-04 22:35 Akira Kakuto
2014-11-05  7:42 Akira Kakuto
2014-11-05  8:14 ` luigi scarso
2014-11-05  9:28 ` Mikael P. Sundqvist
2014-11-05 10:40   ` 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=5458FD05.1070304@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).