On Wed, Jul 29, 2020 at 09:37:13PM -0700, Hans Hagen wrote:
> > One other question about LuaMetaTeX 2.7.1: I noticed that the
> > terminal_input callback is gone. Does this mean that the current
> > behaviour of basically freezing when previously terminal input was
> > requested is hardcoded or is
On 7/29/2020 6:11 PM, Marcel Fabian Krüger wrote:
there have been a couple of bug fixes after the formal 5.4.0 release but afaik
not in the virtual machine code (which normally is the most sensitive); i used
to mark low level changes so that it got signaled (in context) but the byte
code versi
> there have been a couple of bug fixes after the formal 5.4.0 release but
> afaik not in the virtual machine code (which normally is the most sensitive);
> i used to mark low level changes so that it got signaled (in context) but the
> byte code version info changed late in 5.4 dev so i no long
On 7/29/2020 6:22 AM, Marcel Fabian Krüger wrote:
Hi,
starting with LuaMetaTeX 2.07.01, a C library I load from Lua started to
segfault and valgrind indicates that it accesses invalid memory in
multiple places in the middle of Lua internal functions?!
The whole thing looks almost like the Lua v
Hi,
starting with LuaMetaTeX 2.07.01, a C library I load from Lua started to
segfault and valgrind indicates that it accesses invalid memory in
multiple places in the middle of Lua internal functions?!
The whole thing looks almost like the Lua versions in LuaMetaTeX and in
the library are incompa
