From: "Lukáš Procházka" <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Ctx goes into infinite loop?
Date: Sun, 25 May 2014 13:33:35 +0200 [thread overview]
Message-ID: <op.xgeyd9xmf14xzu@lkzd-2013> (raw)
In-Reply-To: <537F58B9.3070005@gmx.net>
Hello,
I solved the problem.
I was "requiring" a Lua .dll at some place in Ctx \s...luacode, namely LuaXml_Lib.dll.
I didn't realize that Ctx found the lib, but that have been compiled for Lua 5.1.
So, with my "ancient" Ctx version (5/2012, which I've been using often so far), all worked well as LuaXml_Lib was compatible with that version of Ctx.
Once I tried the latest Ctx beta, there was a failure;
and it appeared like "cannot locate file ... " error.
I built a Lua 5.2 version of LuaXml_Lib and all works well now with the latest Ctx.
- If some interested why I'm using LuaXml_Lib with Ctx, when Ctx provides its own XML API,
the reason is that I often save Excel tables as "Excel XML table" to allow Lua scripts access them, especially I'm using Excel "named regions/variables" which are later transformed into Lua tables.
I need an independent XML tool for this; LuaXML_Lib (http://viremo.eludi.net/LuaXML) does the job.
And also I need to do similar things with Ctx;
thus I need LuaXML_Lib to be accessible from within Ctx.
- Question: when is Ctx supposed to adopt Lua 5.3?
Best regards,
Lukas
On Fri, 23 May 2014 16:18:33 +0200, Peter Rolf <indiego@gmx.net> wrote:
> Am 23.05.2014 13:50, schrieb Hans Hagen:
>> On 5/23/2014 1:30 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
>>> Hello,
>>>
>>>>> \input \HOME/Common/_Defs_.ctx
>>>>
>>>> at least put { } around the input name
>>>
>>> --
>>> \startluacode
>>> local home = (os.getenv("HOME.ORG") or os.getenv("HOME") or
>>> "?"):gsub("\\", "/")
>>>
>>> context.setvalue("HOME", home)
>>> \stopluacode
>>>
>>> \input{\HOME/Common/_Defs_.ctx}
>>>
>>> \starttext
>>> Test
>>> \stoptext
>>>
--
Ing. Lukáš Procházka [mailto:LPr@pontex.cz]
Pontex s. r. o. [mailto:pontex@pontex.cz] [http://www.pontex.cz]
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751
Fax: +420 244 461 038
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-05-25 11:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 10:40 Procházka Lukáš Ing. - Pontex s. r. o.
2014-05-23 11:15 ` Hans Hagen
2014-05-23 11:30 ` Procházka Lukáš Ing. - Pontex s. r. o.
2014-05-23 11:50 ` Hans Hagen
2014-05-23 14:18 ` Peter Rolf
2014-05-23 16:01 ` Peter Rolf
2014-05-25 11:33 ` Lukáš Procházka [this message]
2014-05-25 16:33 ` Hans Hagen
2014-05-28 9:26 ` Ctx & Lua 5.3 (was: Ctx goes into infinite loop?) Procházka Lukáš Ing. - Pontex s. r. o.
2014-05-28 11:47 ` Ctx & Lua 5.3 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=op.xgeyd9xmf14xzu@lkzd-2013 \
--to=lpr@pontex.cz \
--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).