From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: ntg-context@ntg.nl
Subject: Re: Different versions of Lua and error in the same versions of ConTeXt (Fedora vs Win7)
Date: Sun, 22 Feb 2015 20:40:52 +0100 [thread overview]
Message-ID: <54EA30C4.2050707@gyza.cz> (raw)
In-Reply-To: <54EA23A4.3000207@wxs.nl>
Hans, thanks for the reply. You write about the embedded CSV scanner. I
was looking at contextgarden and on the Internet too, but I did not
found any information about this.
Can you, please, about built-in scanner CSV say more (link, minimal
example etc.)? This thing interests me very much...
Thanks
Jaroslav Hajtmar
Dne 22.2.2015 v 19:44 Hans Hagen napsal(a):
> On 2/22/2015 7:36 PM, Jaroslav Hajtmar wrote:
>> Hi ConTeXist...
>> How can I find out what version of Lua uses ConTeXt TeXlive 2014
>> respectively what version of Lua uses Standalone ConTeXt?
>> The point is that Pablo Rodriguez use Fedora 20, which comes with
>> Lua-5.2.2. Pablo tested last version of my module ScanCSV and his
>> current version of standalone ConTeXt gained mistake, while I compiled
>> (with the same current version of Standalone under Win7) the same source
>> code without error ....
>>
>> Error message from log file is:
>>
>> t-scancsv-2015-02-19.lua:81: assertion failed!
>> stack traceback:
>> [C]: in function 'assert'
>> t-scancsv-2015-02-19.lua:81: in function 'ParseCSVLine'
>> t-scancsv-2015-02-19.lua:123: in function 'parsecsvdata'
>> t-scancsv-2015-02-19.lua:180: in function 'opencsvfile'
>> [\directlua]:1: in main chunk
>
> _VERSION
>
> for pablo: there are csv scanners built in context
>
> -----------------------------------------------------------------
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2015-02-22 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 18:36 Jaroslav Hajtmar
2015-02-22 18:44 ` Hans Hagen
2015-02-22 19:40 ` Jaroslav Hajtmar [this message]
2015-02-22 20:42 ` Pablo Rodriguez
2015-02-23 8:36 ` Hans Hagen
2015-02-23 8:49 ` Hans Hagen
2015-02-23 9:25 ` Jaroslav Hajtmar
2015-02-24 13:13 ` Jaroslav Hajtmar
2015-02-24 13:46 ` Hans Hagen
2015-02-23 0:10 Akira Kakuto
2015-02-23 5:32 ` Jaroslav Hajtmar
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=54EA30C4.2050707@gyza.cz \
--to=hajtmar@gyza.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).