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
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,
age 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 ther
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&q
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 po
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 to
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.
>
> luamet
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 is of
“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
Jairo :)
>
> El 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 sup
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 to
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
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
> >
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-font
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 ve
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
> > requ
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 some other callback invoked which can then
provide some tokens?
first line on co
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
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 are
g edge
> mkiv : when 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
kiv : when 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
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 to
sole" 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
order for this to work I used with previous versions
the "--nonstopmode --batchmode --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 t
s to work I used with
> previous versions
>
> the "--nonstopmode --batchmode --silent --noconsole" compilation options.
Somewhat related question: is there a way to get rid of the
“This is LuaMetaTeX, Version 2.06.18 “
l
>
> For the second time we will held the meeting at the friendly farm U Škodů,
> at the eastern border of Prague. See the gallery from 2018
> <http://kostverlorenvaart.nl/context2018/> by Frans Goddijn.
>
> Topics will cover usage and development of LuaMetaTeX, ConTeXt, and
t file 'lang-mis.mkxl' is not found, quitting
resolvers | formats |
resolvers | formats | binary path :
/Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
resolvers | formats | format path :
/Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/conte
solvers | formats |
resolvers | formats | binary path :
/Users/hansm/TeX/context-lmtx/tex/texmf-osx-64/bin
resolvers | formats | format path :
/Users/hansm/TeX/context-lmtx/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luametatex
re
0)--(100,0) dashed withdots;
> \stopMPpage
>
> When run through LuaMetaTeX produces a PDF about which Acrobat complains:
>
> The dimensions of this page are out-of-range. Page content might be
> truncated.
>
> and Adobe InDesign cannot handle it at all (displays emp
gt; \stopMPpage
>
> When run through LuaMetaTeX produces a PDF about which Acrobat complains:
>
> The dimensions of this page are out-of-range. Page content might be
> truncated.
>
> and Adobe InDesign cannot handle it at all (displays empty).
>
> The error message stays with
>
The following code:
\startMPpage[instance=doublefun]
draw (0,0)--(100,0) dashed withdots;
\stopMPpage
When run through LuaMetaTeX produces a PDF about which Acrobat complains:
The dimensions of this page are out-of-range. Page content might be
truncated.
and Adobe InDesign cannot
ln -s /usr/local/texlive/2020/texmf-dist/tex
> ~/lmtx/tex/texmf-modules/tex
> >
> > and similar (lmtx is my directory for the standalone).
> >
> > LuaTeX finds files without any issues. However LuaMetaTeX gives the
> > following error:
>
optext
> >
> > works almost perfectly. However, the cross-reference does not work, even
> if the number of the enumeration is displayed correctly. The example fails
> both in LuaTeX and LuaMetaTeX. As I remem
However, the cross-reference does not work, even if
> the number of the enumeration is displayed correctly. The example fails both
> in LuaTeX and LuaMetaTeX. As I remember, the problem appeared as early as
> 2019, so not a matter of a bad
}{\input ward}
\stopproposition
\in[prop:1]
\stoptext
works almost perfectly. However, the cross-reference does not work, even if
the number of the enumeration is displayed correctly. The example fails
both in LuaTeX and LuaMetaTeX. As I remember, the problem appeared as early
as 2019, so not a matter of
following gives wrong outputs both in LuaTeX and LuaMetaTeX:
\starttext $\sqrt{3}$ \stoptext
The beta date is 2020.7.5. Thank you very much.
Jairo :)
___
If your question is of interest to others as well, please add
The following gives wrong outputs both in LuaTeX and LuaMetaTeX:
\starttext $\sqrt{3}$ \stoptext
The beta date is 2020.7.5. Thank you very much.
Jairo :)
___
If your question is of interest to others as well
ist/tex ~/lmtx/tex/texmf-modules/tex
> >
> > and similar (lmtx is my directory for the standalone).
> >
> > LuaTeX finds files without any issues. However LuaMetaTeX gives the
> > following error:
> >
> > runtime error : input file (name of file) is not fou
/local/texlive/2020/texmf-dist/tex ~/lmtx/tex/texmf-modules/tex
>
> and similar (lmtx is my directory for the standalone).
>
> LuaTeX finds files without any issues. However LuaMetaTeX gives the
> following error:
>
> runtime error : input file (name of file) is not found, qui
are welcome.
The download feature for binary files is broken, at least a leading
newline is prefixed to the download. But even then
https://source.contextgarden.net/source/luametatex/luametatex-source.tar.xz
is corrupted.
just ignore it ... it's just a left over crap file from some test
wnload feature for binary files is broken, at least a leading
newline is prefixed to the download. But even then
https://source.contextgarden.net/source/luametatex/luametatex-source.tar.xz
is corrupted.
Cheers,
--
Leah Neukirchenhttps://
nd similar (lmtx is my directory for the standalone).
LuaTeX finds files without any issues. However LuaMetaTeX gives the
following error:
runtime error : input file (name of file) is not found, quitting
The same result is for modules, .sty files and .tex files. Is this
intentional, a bug in LMT
ased on an article Taco wrote 2002
for MAPS.
The solution is to get rid of the old commands and focus on LuaTeX and
LuaMetaTeX solutions because the second allows different TeX code. The
following example shows one of these differences.
% LuaTeX
\def\mycommand
{\ifxxx
\expandafter\
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
Hi all,
I have a bash script which converts a CSV file into a Lua table, which is then
used in ConTeXt.
It works fine, but I wonder whether there is a code within LuaMetaTeX for doing
this directly there (writing a new file which contains the Lua table). This
would be more efficient and neater
On Fri, Jul 03, 2020 at 09:56:28PM +0200, Hans Hagen wrote:
> On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
> > Hi,
> >
> > I recently noticed some cases where luametatex behaved in unexpected
> > ways:
> >
> >- The "Extra \fi&q
On 7/3/2020 2:55 PM, Marcel Fabian Krüger wrote:
Hi,
I recently noticed some cases where luametatex behaved in unexpected
ways:
- The "Extra \fi" error isn't triggered, instead an extra `\fi`
freezes luametatex. (Can be reproduced by compiling a document which
onl
Hi,
I recently noticed some cases where luametatex behaved in unexpected
ways:
- The "Extra \fi" error isn't triggered, instead an extra `\fi`
freezes luametatex. (Can be reproduced by compiling a document which
only consists of a single \fi)
- token.new can only cr
is not possible in TeX
> > >
> > > \def#1\macro{blabla#1}
> > >
> > > where arguments come before. The only partial exceptions are commands
> > > like \atop or \over, which are in fact primitives. Is there a way to
> do
> > > this in ConTeXt?
&g
;
> > where arguments come before. The only partial exceptions are commands
> > like \atop or \over, which are in fact primitives. Is there a way to do
> > this in ConTeXt?
> >
> > Could it be a feature request for LuaMetaTeX? I've seen Hans
> > experimenting
ad the following is not possible in TeX
> >
> > \def#1\macro{blabla#1}
> >
> > where arguments come before. The only partial exceptions are commands
> > like \atop or \over, which are in fact primitives. Is there a way to do
> > this in ConTeXt?
> >
> > Co
be a feature request for LuaMetaTeX? I've seen Hans
experimenting a lot with new primitives and new possibilities for
arguments, like #0 and co., so I ask in case it's not too nonsensical to
propose it. Regards
Every \foo will be looked up, so by the time \macro in:
bla bla {\bf
I've read the following is not possible in TeX
\def#1\macro{blabla#1}
where arguments come before. The only partial exceptions are commands like
\atop or \over, which are in fact primitives. Is there a way to do this in
ConTeXt?
Could it be a feature request for LuaMetaTeX? I've
d nodes: 62 nodes, 12 lists of 443
mkiv lua stats > node memory usage: 64 attribute, 30 attribute_list, 1 glue,
51 glue_spec, 3 kern, 2 penalty, 2 temp, 2 whatsit
mkiv lua stats > node list callback tasks: 8 unique task lists, 7 instances
(re)created, 464 calls
mkiv lua stats > used
not much (measurable) to gain at the macro level wrt speed. Most
bottlenecks are at the Lua end anyway.
(1) macro arguments:
In tex a macro argument is defined with numbers, so
\def\foo#1#2{... #2 ... #2 ...}
in luametatex we can have some variants
#0 : the argument is picked up but not s
On 6/17/2020 4:24 PM, Marcel Fabian Krüger wrote:
How does this work with mark nodes? Their mark field has a table
containing triples of command, character and "cs" value. How can the
actual csname of a controlsequence be extracted from this in LuaMetaTeX?
at the token ends marks are
gt; > > again
> > >
> > > > Beside that, I noticed a smaller weird thing when using LuaMetaTeX in
> > > > ini
> > > > mode without Context: The default mathcodes for digits and letters have
> > > > their class and family values switched.
On 6/17/2020 12:10 PM, Marcel Fabian Krüger wrote:
On Mon, Jun 15, 2020 at 04:16:06PM +0200, Hans Hagen wrote:
ah, i removed some doee that i though was never seen; i'll add that bit
again
Beside that, I noticed a smaller weird thing when using LuaMetaTeX in ini
mode without Context
ue?
>
> Many thanks for your help,
>
> Pablo
Hi Pablo,
I fear I don't understand what issue you mean, therefore I append my output
here.
I'm using:
LuaMetaTeX, Version 2.04.02
ConTeXt ver: 2020.02.17 19:36 MKIV beta fmt: 2020.2.23
Best wis
Hi,
in the latest luametatex version, \the\font does ... something weird:
E.g. with a current, fully updated lmtx, I get for
\starttext
\showthe\font
\stoptext
the output
> }\ifempty \currentstyleparameter \else \dousecurrentstyleparameter \fi
instead of the expected
> \3>modern-d
On 6/11/2020 10:47 PM, Marcel Fabian Krüger wrote:
The following document:
\starttext
\def\mymacro#1 bc{}
{\mymacro a b bc}
\stoptext
used to work and lead to no output. But in the new luametatex version,
it complains about "! Argument of \mymacro has an extra }" as if it
doesn'
ors and ^^ is the only way to get
that without introducing actual changes to behavior.
I had another issue with the latest luametatex:
The following document:
\starttext
\def\mymacro#1 bc{}
{\mymacro a b bc}
\stoptext
used to work and lead to no output. But in the new luametatex version,
it complain
I run the "Userland" App from Playstore.
That App integrates well with Android.
I can edit with vim in the kali linux terminal or with any other Editor for
Android like Jota+.
I can try to compile the luametatex manual and send you the results.
Greetings Lutz
Am 10. Juni 2020 19:
, but how
about the disk. How do you edit on such a device?
(Over the time lmtx became more efficient in terms on memory (access)
and such. Compiling the luametatex manual on the RPI 4 (somewhat
overclocked) takes 3 times when my laptop does which I consider okay,
although the aim of course is
LuaMetaTeX, Version 2.06.07
system > ConTeXt ver: 2020.06.10
Seems OK to me.
I get the same result with LuaTeX+MkIV 2020-05-08 and LMTX 2020-06-10,
even commenting out \dontleavehmode.
The only difference is the figure color: blue for LMTX, yellow for MkIV.
Ma
LuaMetaTeX, Version 2.06.07
system > ConTeXt ver: 2020.06.10
No problem here (but the version from May a problem).
mtx-context | current version: 2020.06.10 12:26
Wolfgang
___
If your question is
figure-framedtext.tex
In the above example the fix is to add \dontleavehmode between the figue and
the framedtext. If one comments out that line then the issue can be seen.
Thanks in advance for any help: Otared K.
can others confirm this
This is LuaMetaTeX, Version 2.06.07
system
that we get a more meaningful
> and robust subsystem (basically getting rid of funny numbers) ... this
> also will be discussed in an evenmore chapter .. not that users need it
> (i think)
>
> - as a side effect (or necessity) some low level recoding (and
> abstraction) had to hap
broken) .. in the end it was all doable
because most of the preparation was already done over the last years
- in the process we got rid of a traditional tex data structure that was
left over from the 32 bit times but no longer needed in our 64 bit
luatex/luametatex universe (i might backport th
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, but LTL is broken for Manchu
script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does
not support vertical direc
Hi list! I'm curious about vertical typesetting in ConTeXt. As far as I
know, LuaTeX supports four text directions, but LTL is broken for Manchu
script (letters are displayed unjoined in LTL mode) and LuaMetaTeX does not
support vertical directions anymore, at least as primitives.
I foun
11:34 AM, Otared Kavian wrote:
>> Hi all,
>> When I run
>> sh install.sh
>> in order to update my installation of LuaMetaTeX, I keep getting version
>> 2020.05.25 23:39.
>> Is this the latest version, or have I an issue with the install script?
> There hav
On 6/7/2020 11:34 AM, Otared Kavian wrote:
Hi all,
When I run
sh install.sh
in order to update my installation of LuaMetaTeX, I keep getting version
2020.05.25 23:39.
Is this the latest version, or have I an issue with the install script?
There have been no updates last week ... there
Hi all,
When I run
sh install.sh
in order to update my installation of LuaMetaTeX, I keep getting version
2020.05.25 23:39.
Is this the latest version, or have I an issue with the install script?
Thanks in advance for any help: Otared K
In the current beta ( LuaMetaTeX, Version 2.06.05),
\m{\frac{28}{8\times29}}
puts the numerator and denominator too close to the dividing line.
Similarly for the variants of \frac and \over.
\m{{28}\over{8\times29}}
Alan
nd development of LuaMetaTeX, ConTeXt, and
everything related. Each meeting is source of inspiration for everybody,
from beginner to expert. Friendly company is always looking for meeting new
participants, users of LuaTeX, LuaMetaTeX, ConTeXt, Metapost, etc.
There is a special discount for those, who a
t; with an ASCII character.
Could this be fixed or is it really a limiatation of Windows?
It depends on the version and engine. [...]
In luametatex things are different. There all windows specific
operations have wide-character support, that is, the utf8 goes via utf16
and codepages and such:
; with an ASCII character.
>>
>> Could this be fixed or is it really a limiatation of Windows?
> It depends on the version and engine. [...]
> In luametatex things are different. There all windows specific
> operations have wide-character support, that is, the utf8 goes via
utf names here) but I trust his (always done) testing
of context. That will trickle into future binaries (which is somewhat
tricky as we have experimental as well as current).
In luametatex things are different. There all windows specific
operations have wide-character support, that is, th
On 5/28/2020 4:03 PM, Marcel Fabian Krüger wrote:
Hi,
I had two issues with luametatex:
The manual documents getters and setters for the directions:
The direction states can be queried and set with:
tex.gettextdir() tex.getpardir() tex.setmathdir()
tex.getlinedir() tex.settextdir
Hi,
I had two issues with luametatex:
The manual documents getters and setters for the directions:
The direction states can be queried and set with:
tex.gettextdir() tex.getpardir() tex.setmathdir()
tex.getlinedir() tex.settextdir() tex.setpardir()
tex.getmathdir() tex.setlinedir
Hi!
LMTX and MkIV behave differently if dots are used in the file
name. Example:
printf '%s\n' '\starttext\null\stoptext' > foo.10.tex && context foo.10.tex
MkIV: → foo.10.pdf
LMTX: → foo.pdf
Is this intentional?
This is LuaMetaTeX, Version 2.06.05
current v
omething changed or is it
a bug?
\starttext
\bTABLE
\bTR
\bTD \samplefile{knuth} \eTD
\bTD \samplefile{knuth} \eTD
\eTR
\eTABLE
\stoptext
This is LuaMetaTeX, Version 2.06.05
current version: 2020.05.25 23:39
Marco
_
addition is easy because already reads the first line of the document
> for special setting (e.g. the engine) but anything which is set in the
> document requires more work because you don't know the new name *before*
> LuaTeX or LuaMetaTeX create the PDF.
You don
;> That contradicts the mode approach. It would be nice if we could set (or can
>> we?) the result from within the product, depending on a mode – since the
>> product is renamed only later anyway, that could be viable.
> This addition is easy because already reads the first line of th
be viable.
This addition is easy because already reads the first line of the
document for special setting (e.g. the engine) but anything which is set
in the document requires more work because you don't know
uaTeX, Version 1.13.0 (TeX Live 2021/dev)
> For ConTeXt (LMTX): This is LuaMetaTeX, Version 2.06.03
>
> El mié., 20 de may. de 2020 a la(s) 16:25, Hans Hagen (j.ha...@xs4all.nl)
> escribió:
>
>> On 5/20/2020 10:26 PM, Jairo A. del Rio wrote:
>> > I did. It turns out that i
Info from \luatexbanner
For ConTeXt (LuaTeX): This is LuaTeX, Version 1.13.0 (TeX Live 2021/dev)
For ConTeXt (LMTX): This is LuaMetaTeX, Version 2.06.03
El mié., 20 de may. de 2020 a la(s) 16:25, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 5/20/2020 10:26 PM, Jairo A. del Rio wrote:
> &
ect is not working at all. I get this error:
>>
>> mtx-context | processing extra: mtx-context-select.tex
>> mtx-context | redirect luametatex -> luatex: luatex --luaonly
>> "/opt/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua" --script mtx-context
801 - 900 of 1182 matches
Mail list logo
