From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Multiple cases of unexpected behaviour in luametatex
Date: Sat, 4 Jul 2020 19:18:11 +0200 [thread overview]
Message-ID: <b9c5ee45-13be-5788-c0b4-7b203877cbb4@xs4all.nl> (raw)
In-Reply-To: <20200704052200.hxcaiq2eih4szixz@yoga>
On 7/4/2020 7:22 AM, Marcel Fabian Krüger wrote:
> 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.
The error code has been rewritten but that already happened long ago,
and i never came to hooking the errhelp into that (rather trivial but we
never use that in context anyway), I'll look at it.
> 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?
No, as that is a side effect of the 'rest of the command line being read
after an injected \input' and that is not the case in luametatex. There
are a few command line arguments and --jobname is one of then. That bit
won't change but one can deal with that in Lua (there is an input line
callback so i might even drop the left over bits of those terminal
related features).
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-07-04 17:18 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
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 ` 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=b9c5ee45-13be-5788-c0b4-7b203877cbb4@xs4all.nl \
--to=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).