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>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: luatools not finding files in TL 2010
Date: Mon, 31 May 2010 21:42:42 +0200	[thread overview]
Message-ID: <4C041132.1010706@wxs.nl> (raw)
In-Reply-To: <AANLkTinpDH6GX4QbWWKiX8cmf1oYE1oSSLQLO-pNlWpB@mail.gmail.com>

On 31-5-2010 7:05, Mojca Miklavec wrote:
> Hans,
>
> if I run
>      mtxrun --script patterns --convert
> on TeX Live 2010 it stops working with
>      cannot open : No such file or directory

hm, i generate them using explicit path (call mentioned at the bottom of 
mtx-patterns as i don't want to depend on tex live ... lessons from the 
past have taught me to keep an eye on it

not sure where the message comes from .. do they ship the same mtxrun as 
context does? (i.e. we use different stubs than the other tex things)

> #1 feature request: it would be nice to have a slightly more
> informative feedback
>
> The problem appears in the following line:
>      function scripts.patterns.prepare()
>          dofile(resolvers.find_file("char-def.lua"))
>      end
> inside mtx-patterns.lua since apparently luatools doesn't find char-def.lua

it does here and in my minimals so what fails in tl? i have

LUAINPUTS = .;$CTXDEVLUPATH;$TEXINPUTS;$TEXMF/scripts/context/lua//

>> luatools char-def.lua
> [no response]
>> kpsewhich char-def.lua
> /Users/mojca/soft/texlive/2010/texmf-dist/tex/context/base/char-def.lua
> [kpsewhich finds the file]
>
> In ConTeXt minimals this works fine.
>
> #2 bugfix request: any idea why it fails or how to fix it?

well, i don't have tex live installed as i switched to the minimals ... 
so now you want me to go back in time?

Hans

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


      parent reply	other threads:[~2010-05-31 19:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 17:05 Mojca Miklavec
2010-05-31 17:08 ` Aditya Mahajan
2010-05-31 17:17   ` Mojca Miklavec
2010-05-31 17:19     ` Aditya Mahajan
2010-05-31 17:26       ` Mojca Miklavec
2010-05-31 17:36         ` Aditya Mahajan
2010-05-31 18:03           ` Mojca Miklavec
2010-05-31 18:05             ` Mojca Miklavec
2010-05-31 18:12             ` Taco Hoekwater
2010-05-31 19:59               ` Hans Hagen
2010-05-31 20:13                 ` taco
2010-05-31 19:42 ` Hans Hagen [this message]

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=4C041132.1010706@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=mojca.miklavec.lists@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).