From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problem with 'kpse.find_file'
Date: Fri, 11 Jun 2010 09:27:28 +0200 [thread overview]
Message-ID: <4C11E560.4040306@wxs.nl> (raw)
In-Reply-To: <AANLkTin27PL63tlToFBhJ2qodACQVrb5SilCvOAbnaAg@mail.gmail.com>
On 11-6-2010 3:03, Li Yanrui (李延瑞) wrote:
> 'kpse.find_file' now can not work in MkIV (beta 2010.06.10 15:24). The
> attachment is a minimal example for this. When I compile it, I got the
> following error:
>
> LuaTeX error<main ctx instance>:2: attempt to call field 'find_file'
> (a nil value)
> stack traceback:
> <main ctx instance>:2: in main chunk.
> }inserted text> ...(kpse.find_file ("a", "lua"))
>
> \dodostartluacode ...d \directlua \zerocount {#1}}
>
> l.4 \stopluacode
i need to check it as i though that i overloades kpse vi ametatables
but i didn't check it ... as taco mentioned kpse is not to be used in mkiv
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-06-11 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 1:03 Li Yanrui (李延瑞)
2010-06-11 4:48 ` Khaled Hosny
2010-06-11 7:27 ` 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=4C11E560.4040306@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).