I agree with the optional alternative. If LuaMetaTeX goes (c)leaner, it can
get rid of obsolete constructions made for a pre-Unicode world. Some are
already angry with primitives gone and I think that's positive, but it's
only my opinion.
Jairo :)
El vie., 5 de feb. de 2021 11:38 a
>> @Article{ angerer2016,
>>> author = {Angerer, Philipp and Haghverdi, Laleh and B{\"{u}}ttner, Maren
>>> and Theis, Fabian J and Marr, Carsten and Buettner, Florian},
>>> doi = {10.1093/bioinformatics/btv715},
>>> issn = {14602059},
>>>
context/base/mkiv/mtx-context-combine.tex
resolvers | formats | executing runner 'run luametatex format':
/opt/context/tex/texmf-linux-64/bin/luametatex --jobname="mtx-context-combine"
--fmt=/opt/context/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fo
ont but probably seldom used so side effects
> will go unnoticed, also, texies often have no problem blaming microsoft,
> even when they got it right; of course we have to admit that 'moving
> forward wrt math fonts' didn't come from our community so we just have
> to follow
>
&
have to admit that 'moving
forward wrt math fonts' didn't come from our community so we just have
to follow
now, when we move on (with context + luametatex) to a variants font
scaling model, i need to adapt the math machinery to deal with that ...
this can have side effects as y
ixes iir), the number of digist that the
backend uses, etc
It's whatever ConTeXt standalone has. I don't have any extra Lua installed:
$ luametatex --version
This is LuaMetaTeX, Version 2.08.11
Execute 'luametatex --credits' for credits and version details.
There is NO warr
it old. In the meantime we got etex extensions, which
adds a few more, and then pdftex ades some, as well as omega and after
that of course luatex. In luametatex we dropped some, and added others,
so there we currently have 770 primitives. The increase of number is
partly due to the 166 extra ma
and rounding in different places (just
different concepts).
A teaser (mostly for MF whih probably runs the most demanding jobs):
The luametatex manual has 290 pages and loads quite some fonts (half a
dozen bodyfont setups in order to demo some things with different fonts).
old mechanism: 10.8 sec
d Haghverdi, Laleh and B{\"{u}}ttner, Maren
>> and Theis, Fabian J and Marr, Carsten and Buettner, Florian},
>> doi = {10.1093/bioinformatics/btv715},
>> issn = {14602059},
>> journal = {Bioinformatics},
>> language = {en},
>> number = {8},
>> pages = {1
Fixed in today’s standalone. Many thanks—and best wishes for 2021!!
Alan
On Wed, Dec 30, 2020 at 10:51 AM Alan Bowen wrote:
> In the last few versions of luametatex standalone, paragraphs that were
> once justified now appear ragged right. My insertions of
> \setupparagraphs[align=wi
In the last few versions of luametatex standalone, paragraphs that were
once justified now appear ragged right. My insertions of
\setupparagraphs[align=wide/normal/yes] and \setupalign[wide/normal/yes]
have had no effect. Is there some new coding that is needed to get
justified text?
Alan
100K (1 cm circle with pdf pattern)
290 page luametatex manual: 105M
(ok, latex is probably much more efficient than context but it gives an
idea)
- Switches to trap on certain pathological events. For example I want to trap
when TeX inserts a frozen \relax because a number couldn't b
o A. del Rio wrote:
> > Hi, list.
> >
> > I've tried using the xdecimal library included with LuaMetaTeX and I
> > have some remarks:
> >
> > 1. Shifts are decimal, not binary: 145 >> 1 gives 14.
>
> this is how decnumber defines shift: digits
>
On 12/28/2020 2:33 PM, Jairo A. del Rio wrote:
Hi, list.
I've tried using the xdecimal library included with LuaMetaTeX and I
have some remarks:
1. Shifts are decimal, not binary: 145 >> 1 gives 14.
this is how decnumber defines shift: digits
2. Integer division (//) is not
Hi, list.
I've tried using the xdecimal library included with LuaMetaTeX and I have
some remarks:
1. Shifts are decimal, not binary: 145 >> 1 gives 14.
2. Integer division (//) is not implemented. Is that by design?
3. Following 2, what would be the way to handle integer division
urnal = {Bioinformatics},
> language = {en},
> number = {8},
> pages = {1241--1243},
> title = {{Destiny: Diffusion maps for large-scale single-cell data in R}},
> url = {
> http://bioinformatics.oxfordjournals.org/lookup/doi/10.1093/bioinformatics/btv715
> files/103/Angerer et
el.pdf},
volume = {32},
year = {2016}
}
This log occurs:
❯ context test.lmtx
resolvers | formats | executing runner 'run luametatex format':
~/Library/ConTeXt/tex/texmf-osx-64/bin/luametatex --jobname="test"
--fmt=~/Library/ConTeXt/tex/texmf-cache/luatex-cache/conte
year = {2016}
}
This log occurs:
❯ context test.lmtx
resolvers | formats | executing runner 'run luametatex format':
~/Library/ConTeXt/tex/texmf-osx-64/bin/luametatex --jobname="test"
--fmt=~/Library/ConTeXt/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb15
t.NR()
end
context.stoptabulate()
\stopluacode
\stoptext
These are global. Many come from lua itself, then there are libraries
than come with luametatex. The rest is context specific and again some
are just helper modules. I notices some 6 stray locals that I fixed.
There were also some
main computer.
I just want to know when I should update the Linux version.
You can just try it as parallel installation. Mojca's farm also breeds
the 32 bit binaries. Because luametatex is leaner on memory and less
demanding wrt the cpu, if luatex works, luametatex should also work.
| skipping tex/texmf-linux-aarch64/bin/context
> > mtx-install | skipping tex/texmf-linux-aarch64/bin/mtxrun
> > mtx-install | changed : 0 % : 2696864 :
> > tex/texmf-linux-aarch64/bin/luametatex
> > mtx-install | tex/texmf-linux-aarch64/bin/luametatex, trying aga
| updating tex/texmf-linux-aarch64, 6 files
mtx-install | skipping tex/texmf-linux-aarch64/bin/context
mtx-install | skipping tex/texmf-linux-aarch64/bin/mtxrun
mtx-install | changed : 0 % : 2696864 :
tex/texmf-linux-aarch64/bin/luametatex
mtx-install | tex/texmf-linux-aarch64/bin
-install | skipping tex/texmf-linux-aarch64/bin/context
mtx-install | skipping tex/texmf-linux-aarch64/bin/mtxrun
mtx-install | changed : 0 % : 2696864 :
tex/texmf-linux-aarch64/bin/luametatex
mtx-install | tex/texmf-linux-aarch64/bin/luametatex, trying again:
mtx-install
On 12/17/2020 11:48 AM, Henri Menke wrote:
Dear Hans,
In LuaMetaTeX the directional syntax for boxes
\hbox dir TLT {...}
is no longer supported. Currently this is necessary for PGF because certain
things like shading have to always be typeset in TLT. Is there a simple
workaround
Dear Hans,
In LuaMetaTeX the directional syntax for boxes
\hbox dir TLT {...}
is no longer supported. Currently this is necessary for PGF because certain
things like shading have to always be typeset in TLT. Is there a simple
workaround?
Cheers, Henri
See also: https://github.com/pgf
by turning tabs into
spaces (the alternative is to let the tab token flagged as spacer travel
around which would permits round trip). Makes me wonder I should have
that as option in luametatex (but as I'm now in metapost mode I delay
tha
On 12/9/2020 9:27 AM, Joseph wrote:
Unfortunately after running install.bat script, I see errors at the end
of installation run :
This is LuaMetaTeX, Version 2.05.01 (INITEX)
strange indeed, i'll make a new install to be sure (no cleu where that
bin comes from)
Unfortunately after running install.bat script, I see errors at the end of installation run : This is LuaMetaTeX, Version 2.05.01 (INITEX)(D:/ConTeXt/lmtx/tex/texmf-context/tex/context/base/mkxl/cont-en.mkxl(context.mkxl! Undefined control sequence.l.31 \immutable \edef\contextformat
On 12/4/2020 9:06 PM, Pablo Rodriguez wrote:
Hi Hans,
many thanks for your new upload that fixes the issue with scaled
external figures.
I have just accidentally realized:
\startbodymatter
\component luametatex-preamble
\component luametatex-differences
Hi Hans,
many thanks for your new upload that fixes the issue with scaled
external figures.
I have just accidentally realized:
\startbodymatter
\component luametatex-preamble
\component luametatex-differences
[...]
\stopbodymatter
\startbackmatter
My update log says:
2020-12-04T11:32:59 ConTeXt updated from 2020.12.01T17:52 to
2020.12.03T19:02
2020-12-04T11:32:59 LuaMetaTeX downdated from 2.08.03 20201123 549
to 2.05.01 20200402 491
That is quite a change!
On 12/4/2020 07:01, Hans Hagen wrote:
On 12/4/2020 11:19 AM
m *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
> > this
-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
Ho
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. (An
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
n ConTeXt 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 agai
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
t;, or
similarly, after 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 Referenc
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, af
':
> /usr/local/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 L
than 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
only use simple stuff)
My actual 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...
ill 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 binary is n
inaries 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: wh
so 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 manual takes between 10 and 10.5 sec
(depending on load). On the
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 luame
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.
luatex) 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 \
sname 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 where I expect (as said)
protec
t; 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/mtxrun --script cache
> --er
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 ConT
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
: 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 --make en
sh: /usr/local/conte
erminated 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
> con
MWE.
well, 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 trad
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
x27;t need them, 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 bot
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 latt
ffect.
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
v. de 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
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`,
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
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" -- hello
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 co
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 i
PT Wed Sep 23 14:20: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/conte
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 wrote:
>
&g
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
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 29
t; 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.
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 problem
persists. If
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`,
t;
> With \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
d
of these limitations 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:/
: \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
inte
e check some new stuff as we
don't want 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 fo
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
essbuffer{test}{test}{}
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="t
guage 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)
discussion but anyway ... The first one is an
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 n
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/5fe67e0bfe781
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 f
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 is
f reader > 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-c
701 - 800 of 1179 matches
Mail list logo
