tafun'
and method 'default'
% metapost> loading 'metafun' as 'metafun.mpxl' using method 'default'
% metapost> initializing number mode 'scaled'
% metapost> trace > This is MPLIB for LuaMetaTeX, version 3.11, running
in scaled mode.
% metapost>
Jdh,
Can you please try again with this binary?
https://dl.contextgarden.net/build/luametatex/aarch64-linux/
On Fri, 16 Jul 2021 at 22:16, Alan Braslau wrote:
>
> Freebsd on arm64 is now a Tier 1 architecture. ;-)
I figured out that there are should-be-working-out-of-the-box
orks!
Although now it remains to apply this technique to LuaMetaTeX. Without
access to source code I can't try anything, but the general ideas should
apply:
I used Zig for cross compiling. While Zig is a full fledged programming
language in its own right, it also has the ability to compile C/C++
(wit
aarch64-linux-musl --help
>
>The above are cross compiled (debug) builds of very stripped down
>version of LuaTeX, that I have been experimenting with. They won't
>solve
>the immediate problem, but the cross compiling procedure could be used
>to generate luametatex binaries for this ta
sed
to generate luametatex binaries for this target until a better option is
available. Of course, depending on whether it even works. :)
Michal Vlasák
___
If your question is of interest to others as well, please add an en
\setupinteraction[state=start]
\usemodule[animation]
\starttext
\useMPanimation[menu=yes]{demo}
\stoptext
Placing this excerpt in a file and compiling it I get an error:
$ context animation.tex
resolvers | formats | executing runner 'run luametatex format':
/home/vm/context/tex/texmf-linux-64/bin
n github which would then involve:
-- core context code (with luametatex in source tree too:
tex/texmf-context in the distribution
-- the minimal set of resources: tex/texmf in the distribution
-- binaries (which is the more complex part)
-- modules: texmf/modules
So, basically several re
On 6/29/2021 12:06 PM, Steffen Wolfrum wrote:
When running this mwe with luatex, the command \- could be used to manually
break the line, even though it is set up nothyphenated.
When running luametatex the word does not break:
\setuppapersize[A10]
\showframe
\setuphead[chapter][align
While luametatex works fine, running this mwe with luatex ends in an error:
\startexceptions
con-text
\stopexceptions
\starttext
context
\stoptext
...-64/tex/texmf-context/tex/context/base/mkiv/lang-ini.lua:198: attempt to
call a nil value (global 'sortedhash')
stack traceback
When running this mwe with luatex, the command \- could be used to manually
break the line, even though it is set up nothyphenated.
When running luametatex the word does not break:
\setuppapersize[A10]
\showframe
\setuphead[chapter][align={nothyphenated}]
\starttext
\chapter{abc\-def
Steffen Wolfrum schrieb am 27.06.2021 um 15:55:
uncommenting the following \setupcolors changes magenta to black when running
luatex.
but when running luametatex the footnote is crippled to «error»:
\starttext
\definestartstop[UL][color=magenta]
%\setupcolors[state=stop,conversion=never
uncommenting the following \setupcolors changes magenta to black when running
luatex.
but when running luametatex the footnote is crippled to «error»:
\starttext
\definestartstop[UL][color=magenta]
%\setupcolors[state=stop,conversion=never]% <- bw with lualatex, but «error»
with luameta
\skip0=10pt plus 10pt minus 10pt plus 20pt
test \skip0=10pt plus 10pt plus 20pt minus 10pt
test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
% test \hbox to 10pt to 10pt {x}
\stoptext
compare pdftex and luametatex.
ok. but why does this run fine
\starttext
Test
t
> test \skip0=10pt plus 10pt minus 10pt plus 20pt
>
> test \skip0=10pt plus 10pt plus 20pt minus 10pt
>
> test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
>
> % test \hbox to 10pt to 10pt {x}
>
> \
10pt
test \vrule width 10pt height 10pt depth 10pt depth 10pt height 10pt
% test \hbox to 10pt to 10pt {x}
\stoptext
compare pdftex and luametatex.
Hans
-
Hans Hagen | PRAGMA ADE
gt; Steffen
>
> –––
>
> … $ ~/context-osx-64/tex/texmf-osx-64/bin/mtxrun --script context
> --autogenerate /Users/steffen/Desktop/error_1.tex
>
> resolvers | formats | executing runner 'run luametatex format':
> /Users/steffen/context-osx-64/tex/texmf-osx-64/bin/lu
| executing runner 'run luametatex format':
/Users/steffen/context-osx-64/tex/texmf-osx-64/bin/luametatex
--jobname="error_1"
--fmt=/Users/steffen/context-osx-64/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex/cont-en.fmt
--lua=/Users/steffen/context-
optimizations (so one needs to
run configure scripts) ... in luametatex i try to stay away from that ..
but loading as external lib is of course an option; we already support
zip, gz, tar, lz4, lzma (xz), lzo, xstd but i doubt if in practice they
are used often (zip we need for pdf, gz for some
variant uses the
basic decompressor of the engine (different in lmtx than in mkiv but
that should not matterl i only tested lmtx). The xz one is a bit more
special as it uses the external xz program unless one has limlzma
installed, e.g. in:
tex/texmf-win64/bin/lib/luametatex/lzma
rmula
>> \stoptext
> it's a bug i introduced in the engine .. you can try a newer bin from:
>
> https://dl.contextgarden.net/build/luametatex/
>
>
> -
> Hans Hagen
$A \cup B = X \cap Y$
\startformula
A \bigcup B = X \bigcap Y
\stopformula
\stoptext
it's a bug i introduced in the engine .. you can try a newer bin from:
https://dl.contextgarden.net/build/luametatex
that not all of that is really needed (also because
much of tex math is chisseled in stone and not supposed to be controlled
although in context i suppose we have a bit more freedom) but it simply
fit in the luametatex effort to do so.
Of course there might be math fields that need such things (so
> flushing realpage 7, userpage 6, subpage 7
pages > flushing realpage 8, userpage 7, subpage 8
pages > flushing realpage 9, userpage 8, subpage 9
[Gets stuck at this point, with luametatex using 100% CPU]
3. Fatal error in both cases:
$ /Library/T
/viserion/LMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
context --autopdf --purgeall hans-33''
resolvers | formats | executing runner 'run luametatex format':
/home/viserion/LMTX/tex/texmf-linux-64/bin/luametatex --jobname="hans-33"
--fmt=/home/viserion/LMTX/tex/texmf-cache/lu
mathadaptsize^1_2 x =
> x = \rab\Umathadaptsize^1_2^^1__2 \mathinner{\vrule height 30mm
> depth 30mm width 5mm}
> $
>
> \stoptext
>
> After playing with several solutions (delimiters, fences, radicals etc)
> I just settled for a few line extension to the engine (there
thadaptsize^1_2^^1__2 \mathinner{\vrule height 30mm
depth 30mm width 5mm}
$
\stoptext
After playing with several solutions (delimiters, fences, radicals etc)
I just settled for a few line extension to the engine (there was already
plenty in place in luametatex for that anyway) and it
the are implemented and the way
TeX (the engine) works when it reads arguments.
and, also in mkiv \dofmode is unexpandable so cannot act as keyword
(it might not crash but also doesn't work)
Here is a short example which demonstrates the differences between
LuaTeX (eTeX, pdfTeX etc.) and LuaMetaTeX
}{on}} [[\meaningless\foo]]
only in luametatex/lmtx
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl
>
For me this builds fine with MkIV (TeX Live 2021 on Arch, specifically
2021.58686-3), however TikZ is incompatible with LMTX right now:
https://github.com/pgf-tikz/pgf/issues/990
There I get the following issue which is slightly different than yours
though:
resolvers | forma
\startTEXpage[offset=1ex]
\startitemize
\item \MyURL{a.b\\/c.d\letterhash e}
\stopitemize
\stopTEXpage
\stoptext
I’m using current latest from 2021.06.04 17:28.
LuaTeX generates the link rectangle right.
LuaMetaTeX generates a wrong link rectangle.
In the attached image, you can see
{a.b\\/c.d\letterhash e}
\stopitemize
\stopTEXpage
\stoptext
I’m using current latest from 2021.06.04 17:28.
LuaTeX generates the link rectangle right.
LuaMetaTeX generates a wrong link rectangle.
In the attached image, you can see the output I get (MkIV and LMTX).
Could anyone confirm
to have the sql library in the tex binary tree
(see manual)
(in luatex/mkiv it's best to use the ffi variant that interfaces to
the mysql library; in luametatex/lmtx it's a - by default - build in
optional which loads the lib on demand; in all cases most happens in lua)
so, if it doesn't work
e option
"--purgeall".
This happens both with MkIV (LuaTeX 1.13 7420 + ConTeXt MkIV 2021.06.04
17:28) and LMTX (LuaMetaTeX 2.09 20210531 + ConTeXt LMTX 2021.06.04 17:28).
Contents seem to be irrelevant, but actual contents of "mwe.tex" read:
\starttext
\input zapf
\stopt
appens both with MkIV (LuaTeX 1.13 7420 + ConTeXt MkIV 2021.06.04
17:28) and LMTX (LuaMetaTeX 2.09 20210531 + ConTeXt LMTX 2021.06.04 17:28).
Contents seem to be irrelevant, but actual contents of "mwe.tex" read:
\starttext
\input zapf
\stoptext
I’m afraid that this might be
)
(in luatex/mkiv it's best to use the ffi variant that interfaces to the
mysql library; in luametatex/lmtx it's a - by default - build in
optional which loads the lib on demand; in all cases most happens in lua)
so, if it doesn't work, you have to explain your setup
Hans
gt; loaded fonts: 3 files: latinmodern-math.otf, lmmono10-regular.otf, lmroman12-regular.otf
mkiv lua stats > font engine: otf 3.116, afm 1.513, tfm 1.000, 8 instances, 3 shared in backend, 3 common vectors, 0 common hashes, load time 0.180 seconds
mkiv lua stats > font embedding time: 0.0
n" and "context" are just links to "luametatex" and when
called with a different name than "luametatex" they will try to locate
scripts with their name in the same path (so there need to be
mtxrun.lua and context.lua in that nin path). The mtxrun.lua fil
contains everything that is needed.
In lmtx "mtxrun" and "context" are just links to "luametatex" and when
called with a different name than "luametatex" they will try to locate
scripts with their name in the same path (so there need to be mtxr
nction
0, total: 0 (0 per page)
mkiv lua stats > randomizer: resumed with value 0.41693551017344
mkiv lua stats > loaded tex modules: 5 requested, all found (*-filter
*-module-catcodes *-syntax-groups *-syntax-highlight *-vim)
mkiv lua stats > loaded patterns: en::1, load time: 0.000
mk
Dear list,
For some reason pgfplots has a \pgfkeys invocation where the argument
has more than 4000 lines. This crashes LuaMetaTeX with the message
tex error > tex error on line 4045 in file pgfplots.code.tex: TeX capacity
exceeded, sorry [token memory size=100]
It doesn't s
Il 25/05/21 17:25, Henri Menke ha scritto:
Dear list,
For some reason pgfplots has a \pgfkeys invocation where the argument
has more than 4000 lines. This crashes LuaMetaTeX with the message
tex error > tex error on line 4045 in file pgfplots.code.tex: TeX capacity
exceeded, sorry [to
erribly long. I hope
that’s not bad etiquette. (I’m fairly new here.)
Thanks!
Gavin
> mtx-context | redirect luametatex -> luatex: luatex --luaonly
> "/Users/Gavin/context-osx-64/tex/texmf-osx-64/bin/mtxrun.lua" --script
> mtx-context --luatex --autopdf GlyphExp.
oing the same ... don't worry, i threw
> > away plenty of code by now
> >
> > -- significant performance gain: which is seldom the case (there
> really
> > is not much to gain, at least not in context which is rather
> optimized
> > already)
&g
tracing: which for me is a good reason
(tracing changed a bit anyway)
-- not adding much code to the engine or the need to refactor: although
for some luametatex extensions some internals had to change
fundamentally
a good example is the extended macro argument handling: less clum
ot in context which is rather optimized
> already)
>
> -- giving way less noise in tracing: which for me is a good reason
> (tracing changed a bit anyway)
>
> -- not adding much code to the engine or the need to refactor: although
> for some luametatex extensions some internals
Julian, is the luametatex file in that directory executable?
both context and mtxrun are links to it:
lrwxrwxrwx 1 xxx xxx 10 context -> luametatex
-rw-r--r-- 1 xxx xxx 1315 context.lua
-rwxr-xr-x 1 xxx xxx 2957368 luametatex
-rwxr-xr-x 1 xxx xxx 7150016 luatex
lrwxrwxrwx 1 xxx
giving way less noise in tracing: which for me is a good reason
(tracing changed a bit anyway)
-- not adding much code to the engine or the need to refactor: although
for some luametatex extensions some internals had to change fundamentally
a good example is the extended macro argument hand
On 5/19/2021 9:56 PM, Alan Bowen wrote:
I seem to be stuck at ver. 209.08 (context ver. 2021.04.29).
I downloaded context-osx-64.zip and made a clean install following the
instructions for macOS on the wiki.
context—version showed v. 2021.04.29
So I removed texmf cache and ran
mtxrun
showed ver. 2021.04.29
when I ran
sh install.sh
again, the result was the same. The version installed was still 2021.04.29
But this time the log showed an error
mtx-install | running:
/Users/bowen1/Desktop/LuaMetaTeX/tex/texmf-osx-64/bin/mtxrun --generate
lua error : startup file:
...owen1/Desktop
laptop is from 2013 (decent intel 3840QM cpu + 16 GB
mem and ssd and so) and is about 3 times slower than the rpi 4 in the
luametatex manual.
Your file in mkiv does a decent ppm (is that an arm or intel mac?)
mkiv lua stats > lua properties: engine: lua 5.3, used memory: 601 MB,
ctx: 579 MB,
pen"] =500, -- i use 2000
["luatex.maxprintline"] = 1, -- no need to change
["luatex.maxstrings"]= 50, -- maybe sometimes
["luatex.paramsize"] = 25000, -- seldom
["luatex.savesize"] = 10, -- often an error if more needed
Hi,
With luametatex becoming more mature, it's time to get rid of some old
code. For instance, we have lmt files that assume 5.4, but regular lua
files should work for luajittex (5.2) and luatex (5.3). Most noticable
are the lack of bitwise operators and integer devision in luajittex
On 5/3/2021 5:58 PM, Alan Bowen wrote:
I have re-installed the latest luametatex (macOS) following the
directions on the wiki
(https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS
<https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS>)
Though
luametatex --version
I have re-installed the latest luametatex (macOS) following the
directions on the wiki (
https://wiki.contextgarden.net/Installing_ConTeXt_LMTX_on_MacOS)
Though
luametatex --version
mtxrun --generate
are successful,
context --version
context --make --all
gets
mtxrun | unknown script 'mtx
\exhyphenchar, in luametatex we can tag any char
as such
in traditional tex th ehyphenation, ligature building and kerning wre
integrated, so handling - -- --- -- is kind of complex
in luatex these stages are split but there's still messy logic wrt
successive hyphens
is that (when we go that route) some font
code can be dropped. The impact on luametatex-the-engine is that all
font related dimensions have more complex calculations, and of course
the impact on the math code is even larger because there we also have
the styles to deal with. On the other hand, we no
On Sat, Apr 24, 2021 at 1:33 AM Sylvain Hubert
wrote:
> You're right, I just checked the symbols of luatex and they contain all
> the APIs of lua 5.3.
> So I guess the problem is specific to luametatex and the latest context.
>
> > but in any case you should compile against
You're right, I just checked the symbols of luatex and they contain all the
APIs of lua 5.3.
So I guess the problem is specific to luametatex and the latest context.
> but in any case you should compile against the luatex headers, not the
stock lua 5.3.6.
Does luatex have dedicated head
:
https://dl.contextgarden.net/build/luametatex/win64/
make sure you replace/link luametatex.exe, mtxrun.exe and context.exe so
that all then use the replacement. Mojca also configured the setup for
native 32 bit binaries in case you need those. (The clang variants are
compiled because want
refore luametatex --luaonly can’t execute it.
I suppose we can make it work (because lmtx can call out to kpse if
needed) but it's not worth the trouble because afaiks it depends on
perl, does all kind of map things, probably donwloads more than one
needs and I actually prefer to be explici
Hi!
The LMTX distribution comes with few binaries, texlua being none of them.
The getnonfreefonts <https://www.tug.org/fonts/getnonfreefonts/> script
seems simple enough, but it relies on a global “kpse” which it uses to get
kpse variables. Therefore luametatex --luaonly can’t e
backport some but it probably makes no sense
(some is probably easy). There is of course untested code like the
overload protection mechasnisms but I have that enabled on my machine
(users can do that too) so I can notice side effects.
The new engine (luametatex) doesn't change much. Recent
ications/LuaMetaTeX/tex/texmf-context/te..."]:1343: attempt to
concatenate a boolean value (local 'v')
I did a new upload that fixes is (had to do with 'nicer looking' logging).
Hans
-
Hans H
ications/LuaMetaTeX/tex/texmf-context/te..."]:1343: attempt to
concatenate a boolean value (local 'v')
can you run on a shorter path so that we can see where?
-
Hans Hagen
Files that ran well with ver ConTeXt ver: 2021.02.20 16:50 LMTX and
earlier now fail with the following message:
tex error > tex error on line 74 in file
c_Review-0201-01_Bojowald.tex:
lua error:
run callback [36]: [string
"/Applications/LuaMetaTeX/tex/texmf-context/te..."]:
\luametatex\wincon\wincon.dll
(mtxrun --generate)
maybe
\enabletrackers[resolvers.libraries]
gives you a clue
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt
with
the latest luametatex/lmtx combination. It was crosscompiled on an
intel mac which took ages so it stuck as experiment. Because th eintel
bin runs on the arm mac it has a low priority (unless someone donates
an arm mini to the farm). So, forget about the arm apple bins for now.
We do generate windows
On 2/23/21 6:45 PM, Hans Hagen wrote:
> On 2/23/2021 6:15 PM, kaddour kardio wrote:
>> Thank you Hans and Pablo, symlinking the font directories to luametatex
>> font directory worked as expected. I guess i have to follow the same
>> steps after every update..
> no, beca
On 2/23/2021 6:15 PM, kaddour kardio wrote:
Thank you Hans and Pablo, symlinking the font directories to luametatex
font directory worked as expected. I guess i have to follow the same
steps after every update..
no, because texmf-fonts is never touched by an update
Hans
,
Shade) which is part of the ARM 64bit tree but not in the manual in the
X86 64bits tree.
That arm version was an experiment so it's definitely not in sync with
the latest luametatex/lmtx combination. It was crosscompiled on an intel
mac which took ages so it stuck as experiment. Because th
Thank you Hans and Pablo, symlinking the font directories to luametatex
font directory worked as expected. I guess i have to follow the same steps
after every update..
Le dim. 21 févr. 2021 à 18:42, Pablo Rodriguez a écrit :
> On 2/21/21 5:05 PM, Hans Hagen wrote:
> > On 2/21/202
the metafun manual (but first i need to do the
periodical update of the luametatex manual - kind of boring an dless fun
than metafun)
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27
I need to reinstall luametatex version 2.08.13. Is there a page somewhere
describing how to do this?
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg
On 2/5/2021 5:49 PM, Jairo A. del Rio wrote:
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.
I never
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. m., Hans
,
>>> 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},
>>> journal = {Bioinformatics},
&g
xt/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/formats/luametate
y 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
>
> now, when we move on (with
hat '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 you noticed but these will be d
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 warranty. Redistribut
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 math related
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, 292M lua, 99M
t;{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 = {1241--1243},
>> title = {
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
)
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 be read. Another
thing I want to trap
iro 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: digit
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 imple
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,
rem
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 al. - 2016 - destiny diffusion
olume = {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/context/5fe67e0bfe781ce0d
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/5fe67e0bfe781ce0dde776fb1556f32e/for
optabulate()
\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 global variables with suspici
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.
Hans
| 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
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
that pondering.)
Hans
601 - 700 of 1150 matches
Mail list logo
