om *everywhere* else in the document. TeX and
ConTeXt "solve" this problem by using a multi-pass approach (in, for
example, 5 passes for the `luametatex` document).
Between each pass, ConTeXt saves this multi-pass data (page
numbers and cross-references) in the `*.tuc` file.
Clearly
; After some *very crude* tests using the `luametatex` and
> > `luametafun` documents, I find that while I *can* stop effective
> > processing at various points in the LuaMetaTeX pipeline, the time
> > difference overall is not really significant enough to bother with
> &g
-functional* requirement to *prove* the
code's correctness this is the heart of what I have to write about.
There is no getting out of this requirement
So, some day it would be very useful to be able to directly embed a
Lua wrapped ANSI-C shared library inside the new LuaMetaTex
However
On 12/2/2020 11:43 AM, Stephen Gaito wrote:
Again, to my knowledge, Lua v5.4 has only one implementation (though
this implementation *can* be compiled for a very wide range of CPU's).
Lua has not many demands ... it can even run on tiny cpu's. It's all
rather plain C code. (And in luametatex
On 12/2/2020 10:40 AM, Stephen Gaito wrote:
Many thanks for your swift and helpful comments.
After some *very crude* tests using the `luametatex` and `luametafun`
documents, I find that while I *can* stop effective processing at
various points in the LuaMetaTeX pipeline, the time difference
is ideal.
As a mathematician writes, what they write gets proof-checked
automatically... in the document they are writing, and by the
typesetting tool they are using for the finished PDF. :-)
ConTeXt (via LuaMetaTex) makes this possible in a way native TeX/LaTeX
never could.
So once again, many ma
Hans,
Many thanks for your swift and helpful comments.
After some *very crude* tests using the `luametatex` and `luametafun`
documents, I find that while I *can* stop effective processing at
various points in the LuaMetaTeX pipeline, the time difference overall
is not really significant enough
ter the page setting has finished but before the PDF
generation "starts".
yes and often something is left over for a next page so it's kind of fluid
QUESTION: Is it possible to use the new LuaMetaTeX callbacks (found in
chapter 10 of the "LuaMetaTEX Reference Manual") to "
l" TeX stages "Mouth",
"Stomach", "page setting", PDF generation tightly "chained"...
This means that there is no "one" place in the code where all macro
expansions have completed but before the page setting "starts", or
similarly,
cal/lib/lua/5.4/cjson.so: undefined symbol: lua_checkstack
even when using the ConTeXt/LuaMetaTeX `--permiteloadlib` switch.
(Note that this Lua-CJSON module does work with the native 5.4 Lua).
(The ConTeXt I am using identifies itself as: ConTeXt ver: 2020.11.25
19:18 LMTX fmt: 2020.11.25
the rpi 4
these also look interesting
e.g.
https://tinker-board.asus.com/prod_tinker-board-2s.html
<https://tinker-board.asus.com/prod_tinker-board-2s.html>
ah, an update, interesting indeed (also some flash on board)
(I just compiled luametatex for windows arm but I lack a MWHE for
test
debian buster installation is still on glibc-2.28. The x86_64 Linux
binaries also use the older 2.28-version which is widely used among many
distros. I would be very happy if I could install a 2.28-version on my ARM
Linux box. Else I have to compile my own glic... or my own mtxrun...
A luametatex
ries also use the older 2.28-version which is widely used among
> many distros. I would be very happy if I could install a 2.28-version on my
> ARM Linux box. Else I have to compile my own glic... or my own mtxrun...
>
> A luametatex binary is needed.
>
> Out of curiosity: what
8-version which is widely used among many
> distros. I would be very happy if I could install a 2.28-version on my ARM
> Linux box. Else I have to compile my own glic... or my own mtxrun...
A luametatex binary is needed.
Out of curiosity: what hardware do you run your li
some machines so all binaries (platforms) should be in sync now. (No
binaries for apples M1 and microsofts SQ2 as we don't have these
machines, so just good old intel and arm it is.)
On my rusty laptop the luametatex manual takes between 10 and 10.5 sec
(depending on load). On the raspberry pi 64
On 11/25/2020 10:12 AM, Giulio Bertellini wrote:
Great. Made a clean install from scratch and now metafun manual compiles
great at first run:
mkiv lua stats > used engine:*luametatex version: 2.0803, functionality
level: 20201123*, format id: 547, compiler: gcc
mkiv lua stats &g
Great. Made a clean install from scratch and now metafun manual compiles
great at first run:
mkiv lua stats > used engine:* luametatex version: 2.0803, functionality
level: 20201123*, format id: 547, compiler: gcc
mkiv lua stats > tex properties: 740024 hash slots used of 2097152,
appro
Hi,
A new upload. Mojca upgraded the build manager and we also updated some
machines so all binaries (platforms) should be in sync now. (No binaries
for apples M1 and microsofts SQ2 as we don't have these machines, so
just good old intel and arm it is.)
On my rusty laptop the luametatex
After running install.bat I see error : This is LuaMetaTeX, Version 2.08.03 2097153(D:/ConTeXt/lmtx/tex/texmf-context/tex/context/base/mkxl/cont-en.mkxl(context.mkxl(syst-ini.mkxl)(norm-ctx.mkxl)(syst-pln.mkxl)(syst-mes.mkxl)(luat-cod.mkxl<+ D:/ConTeXt/lmtx/tex/texmf-context/tex/context/base/m
Dear All
Unable to compile metafun manual with current release of LMTX for linux
X86_64 and RPI 4 (both Raspberry PI OS 32 bit and Manjaro Linux ARM 64).
engine: luametatex version: 2.0802, functionality level: 20201118
tex error > tex error on line 240 in file metafun-positioning.
) a protected macro inside an \(if)csname does
expand which to makes no sense and smells like a bug. Or maybe it was
tricky to catch (the implementation of protected a bit of a hack).
In luametatex protected macros are native and in the process I also
decided to *not* expand them in a \(if)csname
expand which to makes no sense and smells like a bug. Or maybe it was
tricky to catch (the implementation of protected a bit of a hack).
In luametatex protected macros are native and in the process I also
decided to *not* expand them in a \(if)csname where I expect (as said)
protected macros
in/mtxrun: not found
> mtx-install | running:
> /usr/local/context/tex/texmf-openbsd6.8-amd64/bin/mtxrun --generate
> sh: /usr/local/context/tex/texmf-openbsd6.8-amd64/bin/mtxrun: not found
> mtx-install | running:
> /usr/local/context/tex/texmf-openbsd6.8-amd64/bin/context -
On Mon, 9 Nov 2020 at 23:40, Jairo A. del Rio
wrote:
> Hi, Sylvain.
>
> LuaMetaTeX and LuaTeX, the engines used by ConTeXt nowadays, use an
> embedded library, so external compilations/files are not necessary. Just
> out of curiosity, wouldn't it be easier to use a ConTeXt e
Hi, Sylvain.
LuaMetaTeX and LuaTeX, the engines used by ConTeXt nowadays, use an
embedded library, so external compilations/files are not necessary. Just
out of curiosity, wouldn't it be easier to use a ConTeXt environment? E.g.:
\starttext
\startMPcode %\startuseMPgraphic{} if you want to reuse
tx-install |
mtx-install | tex/texmf:0 files with 0 bytes
installed
mtx-install | tex/texmf-context:0 files with 0 bytes
installed
mtx-install |
mtx-install | ConTeXt LMTX with LuaMetaTeX is still experimental and when
you get a cras
y terminated by
> \relax so tex keeps scanning for optional plus|minus keywords and in
> your case runs into "mtxrunjit"
>
> in luametatex we have a slightly different keyword scanner
>
> - in traditional tex it will just push back the 'non valid' keyword and
> continue
>
, the clue is there: you have
you have a \hskip or \vskip someplace that is not properly terminated by
\relax so tex keeps scanning for optional plus|minus keywords and in
your case runs into "mtxrunjit"
in luametatex we have a slightly different keyword scanner
- in traditional te
eck which version you have installed on your computer:
export PATH=$PATH:$HOME/context/tex/texmf-linux-64/bin/ && context
--version && luametatex --version
Of course, you might need no export or adapt $PATH accordingly to your
ConTeXt directory.
Just in case it
ua (just before running mtxrunbin)*
>
> run("patchelf --set-interpreter
> /my-own-dir/opt/glibc-2.23/lib/ld-linux-x86-64.so.2 --set-rpath
> /my-own-dir/opt/glibc-2.23/lib:/usr/lib64 %s", mtxrunbin)
> run("%s --generate",mtxrunbin)
>
&g
erase
--extras="$LMTXEXTRAS"
*mtx-install.lua (just before running mtxrunbin)*
run("patchelf --set-interpreter
/my-own-dir/opt/glibc-2.23/lib/ld-linux-x86-64.so.2 --set-rpath
/my-own-dir/opt/glibc-2.23/lib:/usr/lib64 %s", mtxrunbin)
run("%s --generate",mtx
, also
because they always seem to be busy with something (also the network).
Tex is just juggling some bytes. In the past tex and distributioen were
considered large ... nowadays they are small compared to whatever you
install and run. And in luametatex/context the performance bottleneck is
lua
n --script font --list --all`
>>
>> Expected behavior:
>> Nothing surprising should happen.
>>
>> Actual behavior:
>> Firefox suddenly eats 100% of cpu
>>
>> I've noticed that `context` symlinks to `luametatex`, but the latter
&g
.
It does here (not that i have a lib to test) so maybe check your path:
.../tex-context/tex/texmf-win64/bin/lib/luametatex/foo/libfoo.dll
(put the file there and run mtxrun --generate)
The lua versions should match and there shopuld be the initialer function.
\enabletrackers[*lib*]
gives some
2020 a la(s) 06:44, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 11/4/2020 11:01 AM, Jairo A. del Rio wrote:
> > Hi. I've just read in the LuaMetaTeX manual that --permitloadlib allows
> > loading compiled (.so/.dll) libraries. However, when I try it using
> > ConTeXt I have an e
Nothing surprising should happen.
>
> Actual behavior:
> Firefox suddenly eats 100% of cpu
>
> I've noticed that `context` symlinks to `luametatex`, but the latter
> itself does not trigger the bug, neither do `luatex` or `latex`, so I
On 11/4/2020 11:01 AM, Jairo A. del Rio wrote:
Hi. I've just read in the LuaMetaTeX manual that --permitloadlib allows
loading compiled (.so/.dll) libraries. However, when I try it using
ConTeXt I have an error message (example below):
%hello.tex
\starttext
\startluacode
local hello
Hi. I've just read in the LuaMetaTeX manual that --permitloadlib allows
loading compiled (.so/.dll) libraries. However, when I try it using ConTeXt
I have an error message (example below):
%hello.tex
\starttext
\startluacode
local hello = require"hellolib" -- hellolib.s
On 10/31/2020 3:50 AM, Jairo A. del Rio wrote:
Hi, Hans. The last release is considerably faster for smaller documents
(for larger documents differences seem to be neglectable). Thank you for
such an improvement. However, something is wrong with one manual:
luametatex manual won't compile
Hi, Hans. The last release is considerably faster for smaller documents
(for larger documents differences seem to be neglectable). Thank you for
such an improvement. However, something is wrong with one manual:
luametatex manual won't compile:
156 Beware: the values are always saved
18 UTC
> 2020 x86_64 GNU/Linux
>
> $firefox --version
> Mozilla Firefox 81.0
>
> $context --version
> mtx-context | ConTeXt Process Management 1.03
> mtx-context |
> mtx-context | main context file:
> /opt/luametatex/texmf-context/tex/context/base/mkiv/context
ble to assume that for something like `context
--help` given that no other commands are making a scene when printing help
messages.
What binary are you using for luametatex ? The normal linux 64-bit one from
the lmtx distribution?
Yes, it is.
On Thu, 29 Oct 2020 at 16:43, Taco Hoekwater wr
Process Management 1.03
mtx-context |
mtx-context | main context file:
/opt/luametatex/texmf-context/tex/context/base/mkiv/context.mkiv
mtx-context | current version: 2020.09.15 18:11
mtx-context | main context file:
/opt/luametatex/texmf-context/tex/context/base/mkiv/context.mkxl
it seems likely that there is
something special going on with exactly your computer or your context
installation.
What binary are you using for luametatex ? The normal linux 64-bit one from the
lmtx distribution?
Be
On 10/29/2020 3:18 PM, Sylvain Hubert wrote:
I would consider it more constructive to admit the existence of the bug
and find a way look into the source code of luametatex, since `context
--help` is obviously not a terribly complicated routine to investigate.
As taco mentioned, it's very
I would consider it more constructive to admit the existence of the bug and
find a way look into the source code of luametatex, since `context --help`
is obviously not a terribly complicated routine to investigate.
On Thu, 29 Oct 2020 at 13:56, Taco Hoekwater wrote:
>
>
> > On
mably
> not related to ‘our’ ConTeXt.
>
> You can test that by (temporarily) redirecting the ‘context’ command from
> ‘luametatex’ to ‘ls’ (but keep it at the same path), and see if the problem
> persists. If so, then it is the actual name giving problems, and then can
> you should file a fi
something with
> (or waiting for ?) a shell command called ‘context’, which is presumably
> not related to ‘our’ ConTeXt.
>
> You can test that by (temporarily) redirecting the ‘context’ command from
> ‘luametatex’ to ‘ls’ (but keep it at the same path), and see if the problem
> pers
Hi Taco,
thanks for the suggestions, but as mentioned earlier, `mtxrun --script font
--list --all` triggers the same problem as `context` does.
I guess the problem might have something to do with fonts, but since
`context` aka `luametatex` is not open source yet, I can't analyse further.
Best
rhaps trying to do something with (or
waiting for ?) a shell command called ‘context’, which is presumably not
related to ‘our’ ConTeXt.
You can test that by (temporarily) redirecting the ‘context’ command from
‘luametatex’ to ‘ls’ (but keep it at the same path), and see if the proble
arguments`
2.b or: `mtxrun --script font --list --all`
Expected behavior:
Nothing surprising should happen.
Actual behavior:
Firefox suddenly eats 100% of cpu
I've noticed that `context` symlinks to `luametatex`, but the latter itself
does not trigger the bug, neither do `luatex` or `latex`, so I
ith \convertedcounter you have always the option to change the style of
> the value,
> e.g. number conversion, prefixes etc.
>
> > What's about \newcount&\advance variant? Why it not work?
>
> Short answer: expansion
>
> You're using advance in a place where it is ju
tations with Luametatex but it's better to use
\incrementcounter.
Wolfgang
___
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/listi
: \contextkind is defined in file context.mkiv
installed via first-setup. It is not defined in the file of the same
name installed as part of LMTX. Another, more significant difference,
is loading modules.)
mkiv works with luatex, lmtx needs luametatex
currently the functionality is mostly the same
installed
via first-setup. It is not defined in the file of the same name
installed as part of LMTX. Another, more significant difference, is
loading modules.)
mkiv works with luatex, lmtx needs luametatex
currently the functionality is mostly the same but further development
happens in lmtx
Hi,
There haven't been lmtx updates for while now but there is a reason for
it. On my machine I have luametatex 2.08 (so we jump number) which is in
terms of typesetting the 20201010 version. That version has some
reorganized internals, most have to do with consistency in the token
interface
users to suffer too much from a couple of fundamental new
features.
Is there a patch so the brave can help with testing?
no patch, just wait for an update (luametatex + context lmtx)
Hans
ks.json
> {
> "name" : "context",
> "tasks" : [
>{
>"label": "ConTeXt LuaMetaTeX",
>"type": "shell",
>"command": "export
> PATH=$HOME/ConTeXt-lmtx/tex/texmf-
here, I think):
%%% Begin of file $HOME/.config/Code/User/tasks.json
{
"name" : "context",
"tasks" : [
{
"label": "ConTeXt LuaMetaTeX",
"type": "shell",
"command": "export
PATH=$H
}{}
The process just stops in the middle. This is the error message from the
live version from the homepage:
resolvers | formats | executing runner 'run luametatex format':
/opt/context/lmtx/tex/texmf-linux-64/bin/luametatex --jobname="texweb"
--fmt=/opt/contex
zero)
but wolfgangs suggestions are the ones to follow ... language=0 is a
hack, just as is setting left/right hyphenmin so we now have a proper
disabler (in luametatex/lmtx that is; luatex/mkiv should not be affected)
Hans
overview of the three successive context versions. The second one is
about the state of luametatex and the third discusses a couple of things
introduced last year (luametatex and lmtx). The tokens talk is for low
level tex lovers (or those who need to impress other texies with token
speak), an
Hi, Otared—
I had
#!/bin/zsh
#set path= ($path /usr/texbin
/Applications/LuaMetaTeX/tex/texmf-osx-64/bin)
export
PATH=~/context-osx-64/tex/texmf-osx-64/bin:~/context-osx-64/bin:~/context-osx-64/tex/texmf-osx-64/bin
~/context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate --script
context
Hi Alan,
Where did you install LuaMetaTeX?
For instance my LuaMetaTeX.engine contains the following three lines:
#!/bin/bash
export
PATH=/context-osx-64/tex/texmf-osx-64/bin:/context-osx-64/bin:/context-osx-64/tex/texmf-osx-64/bin
/context-osx-64/tex/texmf-osx-64/bin/mtxrun --autogenerate
No, Hraban, and I have never had a directory /Users/bowen1/context-osx-64.
Does Luametatex 2.10 (Context 2020.09.03) now require one?
Alan
On Sat, Sep 5, 2020 at 10:26 AM Henning Hraban Ramm wrote:
>
>
> > Am 05.09.2020 um 16:08 schrieb Alan Bowen :
> >
> > When
64/tex/texmf-osx-64/bin/mtxrun
>
> resolvers | formats | executing runner 'run luametatex format':
> /Applications/LuaMetaTeX/tex/texmf-osx-64/bin/luametatex --jobname="Version"
> --fmt=/Applications/LuaMetaTeX/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776f
When I process
\starttext
Hello, world!
\stoptext
I get the following error message:
/Users/bowen1/Library/TeXShop/Engines/LuaMetaTeX.engine:9: no such file or
directory: /Users/bowen1/context-osx-64/tex/texmf-osx-64/bin/mtxrun
resolvers | formats | executing runner 'run luametatex format
Hi,
with the latest LuaMetaTeX upload (running on Linux x64),
\normalunexpanded tries to write to address 0 and therefore
segfaults:
\normalunexpanded{abc}
\starttext
\stoptext
ConTeXt fails with
mtx-context | fatal error: return code: 139
The most interesting message from valgrind
der > cff > unknown local call 314, case 2 : [300 -12] n=2
otf reader > cff > unknown local call 607, case 2 : [-99 -66 99 174]
n=4
otf reader > fatal error in file 'SourceCodeVariable-Roman.otf':
...e0dde776fb1556f32e/formats/luametatex/font-cff-macro.lua:15
On Tue, Aug 25, 2020 at 04:48:27PM +0200, Hans Hagen wrote:
> > I noticed that recent LuaMetaTeX versions treats control sequences
> > defined using token.set_lua with `value` or `condition` as frozen and
> > does not allow redefining them. Given that these are not macros,
is not that large in luametatex.
When mem gets increased, there is a message. We can use that to
eventually determine the best values. Actually we might even lower some
initial values (not that it matters much, lua uses more).
Of course there is also
--timing
but that one has been there from
On 8/25/2020 3:59 PM, Marcel Fabian Krüger wrote:
Hi,
I noticed that recent LuaMetaTeX versions treats control sequences
defined using token.set_lua with `value` or `condition` as frozen and
does not allow redefining them. Given that these are not macros, we also
can't "unfreeze"
Hi,
I noticed that recent LuaMetaTeX versions treats control sequences
defined using token.set_lua with `value` or `condition` as frozen and
does not allow redefining them. Given that these are not macros, we also
can't "unfreeze" them using \unletfrozen.
1. Would it be possi
Thank you for fixing this!
On Thu, Aug 13, 2020 at 02:31:51PM +0200, Marcel Fabian Krüger wrote:
> Hi,
>
> in the current luametatex upload, \scantokens (and also \scantextokens)
> behave odd: They seem to act like \detokenize, except that spaces get
> catcode other instead o
On 8/13/2020 2:31 PM, Marcel Fabian Krüger wrote:
in the current luametatex upload, \scantokens (and also \scantextokens)
behave odd: They seem to act like \detokenize, except that spaces get
catcode other instead of catcode space:
\starttext
\edef\abc{\scantokens{\relax}}
\abc
\edef\abc
Hi,
in the current luametatex upload, \scantokens (and also \scantextokens)
behave odd: They seem to act like \detokenize, except that spaces get
catcode other instead of catcode space:
\starttext
\edef\abc{\scantokens{\relax}}
\abc
\edef\abc{\scantextokens{\relax}}
\abc
\stoptext
used
t name it knows that it has to start in lua mode.
>
> On windows there are two small stubs: mtxrun.exe and context.exe an both will
> start luatex (no need for texlua there) with the same script etc.
>
> In a luametatex setup we have a uniform and simpler model.
>
>
there) with the same script etc.
In a luametatex setup we have a uniform and simpler model.
luametatex : binary
mtxrun : a copy of luametex or symlink to it
context : a copy of luametex or symlink to it
mtxrun.lua : used when mtxrun is started
context.lua : used when
Jairo A. del Rio schrieb am 08.08.2020 um 17:17:
Hi again!
When context --luatex is used with current version: 2020.08.07 23:37
LuaMetaTeX is still used. --engine=luatex has no effect, either. Is that
a bug? Thanks
I have no problems using LuaTeX on Windows.
You can try a new installation
Hi again!
When context --luatex is used with current version: 2020.08.07 23:37
LuaMetaTeX is still used. --engine=luatex has no effect, either. Is that a
bug? Thanks
Cordially,
Jairo :)
___
If your question
the “tasks":[ ] and save it.
> (You have to modify the "texmf-osx-64/bin” path in the following script
> from your machine.
>
> {
> "label": "ConTeXt LuaMetaTeX",
> "type": "shell",
> "command": "expor
ipt from
your machine.
{
"label": "ConTeXt LuaMetaTeX",
"type": "shell",
"command": "export
PATH=/Users/graph/ConTeXtLM/tex/texmf-osx-64/bin:$PATH;mtxrun --autogenerate
--script conte
mié., 10 de jun. de 2020 a la(s) 02:30, Hans Hagen (j.ha...@xs4all.nl)
> escribió:
>
>> On 6/10/2020 7:49 AM, Jairo A. del Rio wrote:
>> > Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I
>> > know, LuaTeX supports four text directions, bu
On 8/3/2020 7:57 PM, Marcel Fabian Krüger wrote:
Hi,
recent LuaMetaTeX versions no longer automatically resize the fontdimen
arrays on assignments.
indeed, using font dimens for other purposes than fonts is pre-etex
hackery that (c|sh)ould have been abandoned decades ago
Is there a way
Hi,
recent LuaMetaTeX versions no longer automatically resize the fontdimen
arrays on assignments.
Is there a way to manually resize them or is it necessary to reload a
patched font you want more fontdimens?
Also, there is an issue with the error message (I guess) for font.setfontdimen
ur kardio schrieb am 02.08.2020 um 11:02:
> > Hi, i am running the latest luametatex 2.07.2 from [aur] repos in my
> > archlinux machine, i got this error when trying to update my font lists
> >
> > (lmtx) ➜ ~ mtxrun --script fonts --reload
> >
kaddour kardio schrieb am 02.08.2020 um 11:02:
Hi, i am running the latest luametatex 2.07.2 from [aur] repos in my
archlinux machine, i got this error when trying to update my font lists
(lmtx) ➜ ~ mtxrun --script fonts --reload
mtxrun | unknown
Hi, i am running the latest luametatex 2.07.2 from [aur] repos in my
archlinux machine, i got this error when trying to update my font lists
(lmtx) ➜ ~ mtxrun --script fonts --reload
mtxrun | unknown script 'fonts.lua' or
'mtx-fonts.lua
On 7/31/2020 6:17 PM, Marcel Fabian Krüger wrote:
Hi,
thanks for handling
f file consition in LuaMetaTeX. While playing with that, I encountered a
potential bug in the latest LuaMetaTeX version: If handle_error_hook is
executed and returns any number, LuaMetaTeX segfaults. (I'm pretty sure
Hi,
thanks for handling
f file consition in LuaMetaTeX. While playing with that, I encountered a
potential bug in the latest LuaMetaTeX version: If handle_error_hook is
executed and returns any number, LuaMetaTeX segfaults. (I'm pretty sure
that this still worked with the previous version
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
> >
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 some other callback invoked which can then
provide some tokens?
first line on console
s quite stable and reliable (given the massive amount of lua
> code that we use in context) ... so, normally patience - read: wait for
> updates - is the answer
Oh I see, I wasn't aware that the dev versions are used. After
recompiling with the latest development code the error is gone.
One othe
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
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
hen possible following lmtx, otherwise frozen
>
> Because we develop lmtx and luametatex alongside it is no problem if we
> have experimental (and even temporary imperfect) code in the engine:
> context knows about it and especially with experiments, we try to make
> sure it doesn'
possible following lmtx, otherwise frozen
Because we develop lmtx and luametatex alongside it is no problem if we
have experimental (and even temporary imperfect) code in the engine:
context knows about it and especially with experiments, we try to make
sure it doesn't hit users (who we don't expect
Jairo A. del Rio schrieb am 23.07.2020 um 19:03:
Hi list! Is --engine=luatex working? Has it changed? The switch seems
to be ignored with newer ConTeXt distributions, so only LuaMetaTeX is
used. Thank you in advance.
context --luatex
Wolfgang
Hi list! Is --engine=luatex working? Has it changed? The switch seems to be
ignored with newer ConTeXt distributions, so only LuaMetaTeX is used. Thank
you in advance.
Jairo :)
___
If your question is of interest
hmode --silent --noconsole" compilation options.
>> Somewhat related question: is there a way to get rid of the
>>“This is LuaMetaTeX, Version 2.06.18 “
>> line on the terminal ?
> Ah, you want to completely hide that tex is used, just in case someone who
> watches a run gets bad feelings (and
701 - 800 of 1145 matches
Mail list logo
