From: "Marcel Fabian Krüger" <tex@2krueger.de>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Multiple cases of unexpected behaviour in luametatex
Date: Sat, 4 Jul 2020 07:22:00 +0200 [thread overview]
Message-ID: <20200704052200.hxcaiq2eih4szixz@yoga> (raw)
In-Reply-To: <7d1f8ca7-2e36-3c99-c729-407a396aa0e2@xs4all.nl>
On Fri, Jul 03, 2020 at 09:56:28PM +0200, Hans Hagen wrote:
> On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
> > Hi,
> >
> > I recently noticed some cases where luametatex behaved in unexpected
> > ways:
> >
> > - The "Extra \fi" error isn't triggered, instead an extra `\fi`
> > freezes luametatex. (Can be reproduced by compiling a document which
> > only consists of a single \fi)
>
> i already fixed here (noticed it when documenting some conditionals)
Great.
>
> > - token.new can only create some `data` tokens, but it doesn't apply
> > bound checking on it's arguments:
>
> there is no checking yet, there is an upper limit of 0x1FFFFF, so i'll add a
> check for that
OK, that explains it.
[...]
>
> eventually i want all to have reasonable ranges in the token interface (not
> per se the same as in the engine itself but that's a black box anyway) which
> involves some offsetting .. i do that stepwise in order to keep a working
> engine (the token interface is not used in context that much)
Please let me know if there is anything I can do to help with that.
Anyway, tehre is another thing I am wondering about: In the latest
luametatex versions, error help strings do not seem to work like they used to.
Especially after \errhelp{some help}\errmessage{error} or
tex.error('fdfd', {'some help'}) in the 'handle_error_hook'
callback, tex.gethelptext returns nil. gethelptext still works for
errors triggered by TeX itself.
One completely different question:
When running luametatex (of course with appropriate format/lua init
script options) but without a TeX file or command, luametatex does not
expect interactive input but instead tries to read the input file
'luametatex.tex'. (Where luametatex does not seem to be hardcoded but
derived from argv[0]) Is there a way to overwrite this default input
file name?
Marcel
___________________________________________________________________________________
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-07-04 5:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 12:55 Marcel Fabian Krüger
2020-07-03 19:56 ` Hans Hagen
2020-07-04 5:22 ` Marcel Fabian Krüger [this message]
2020-07-04 8:33 ` ConTeXt installation on Windows 10 Jean-Pierre Delange
2020-07-04 8:47 ` Wolfgang Schuster
2020-07-04 10:18 ` Jean-Pierre Delange
2020-07-04 13:09 ` Hans Hagen
2020-07-04 17:18 ` Multiple cases of unexpected behaviour in luametatex 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=20200704052200.hxcaiq2eih4szixz@yoga \
--to=tex@2krueger.de \
--cc=j.hagen@xs4all.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).