From: Hans Hagen <j.hagen@xs4all.nl>
To: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: latest lmtx
Date: Sun, 15 Nov 2020 12:47:26 +0100 [thread overview]
Message-ID: <1c2959eb-f8d4-b36b-f018-17f7944aacc3@xs4all.nl> (raw)
In-Reply-To: <72dbb8bc-f8c2-bd83-c555-dfa43e5f9ee1@uni-bonn.de>
On 11/15/2020 12:05 AM, Thomas A. Schmitz wrote:
> On 11/14/20 12:17 AM, j.hagen@xs4all.nl wrote:
>> Take today's upload.
>>
>
> Hi Hans,
>
> since you mentioned that such buglets may occur, here's another one, but
> in this case, the error message is obscure to me, and I have no clue
> where in the environment file it is triggered (it's an xml-project):
>
> tex error > tex error on line 8 in file cont-yes.mkiv: ?
>
>
> lua error:
>
> registered function call [382]: [string "..."]:5: attempt to
> call a nil value (global 'scanintegerargument')
> stack traceback:
> [string "..."]:5: in function <[string "..."]:4>
>
> Does that ring any bell?
>rgrep scanintegerargument *.l*
./toks-scn.lmt 44: local scanintegerargument = scanners.integerargument
./toks-scn.lmt 263: scanintegerargument = scanintegerargument,
so
\ctxlua{print(tokens.scanners.integerargument)}
should print a function reference
if not, you have a mismatch between engine and context files
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-15 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 22:04 Thomas A. Schmitz
2020-11-13 23:17 ` j.hagen
2020-11-14 9:30 ` Thomas A. Schmitz
2020-11-14 23:05 ` Thomas A. Schmitz
2020-11-15 11:47 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-05 14:08 Alan Bowen
2020-09-05 14:25 ` Henning Hraban Ramm
2020-09-05 15:19 ` Alan Bowen
2020-09-05 15:45 ` Otared Kavian
2020-09-05 16:27 ` Alan Bowen
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=1c2959eb-f8d4-b36b-f018-17f7944aacc3@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).