LuaTeX compiling

lualuatexmacrosplain-tex

May someone can explain me how to compile the LuaTeX source files available here :
http://michel.quercia.free.fr/cours-MP.tgz
together with the macro's files
http://michel.quercia.free.fr/montchapet.tgz

On Fedora, I type lualatex cours-MP.tex and here is the log :

This is LuaHBTeX, Version 1.12.0 (TeX Live 2020) 
 restricted system commands enabled.
(./cours-MP.tex
LaTeX2e <2020-02-02> patch level 5
 L3 programming layer <2020-04-06> (./cours.tex (./montchapet.tex
! Undefined control sequence.
l.280 {\let\@tmp\rm\xdef\rm{\@tmp
                               \def\noexpand\euro{{\noexpand\eurofont@rm e}}}

EDIT: an other server to get the files:

https://rpidejr.zapto.org/f/6346ef88c8194da1b1aa/
https://rpidejr.zapto.org/f/28b2a6641ae643cdb01d/

Best Answer

The document is written in PlainTeX, not LaTeX. (How can you tell? The fact that the driver file cours-MP.tex uses \eject and \bye and does not use \documentclass should be a dead giveaway.) Hence, you must use luatex rather than lualatex to compile the file.

Incidentally, on line 267 in the sub-file variable-réelle.tex, one should change =\limits^{\text{def}} to \mathop{=}\limits^{\text{def}} in order to make the code compilable under the current version of LuaTeX. (For TeXLive2021, that's version 1.13.0.)

Aside: As @HenriMenke has pointed out in the comment section, =\limits used to be syntactically legal thru version 0.78 of LuaTeX, distributed with TL2014. (AFAICT, =\limits was never syntactically legal with any version of pdfTeX.) The files provided in the OP's link are all date-stamped 2014 and 2015; this would explain why Michel Quercia was able to get away with writing =\limits. As @HenriMenke further points out, the best fix actually consists of replacing

=\limits^{\text{def}}

with

\mathrel{\mathop{=}\limits^{\text{def}}}

as = is (mostly? always?) a relational operator.

Do be prepared for the first compilation run to require two or more minutes to complete, as the document uses the raster font Concrete Roman. This requires the system to generate lots and lots of gf and pk font files the first time the document is compiled. Any subsequent compilation runs should be much faster.

Related Solutions

[Tex/LaTex] LuaJIT and LuaTeX

I did an attempt a while ago with LuaJIT 1, and it did not seem to be that hard. A few small build tweaks would be needed, but nothing major.

The main reason why there is no LuaJIT in LuaTeX currently is that we have a few patches to Lua now that are not in LuaJIT (and are hard to add) like an extended coroutine subsystem. In lua5.2, our patches to the Lua core will become obsolete, so once we switch to that Lua version, LuaJIT becomes interesting again and I will certainly try to have LuaJIT support by default on the supported platforms. That should be before LuaTeX 1.0, but not in next few months.

But, don't expect much of it. Even in ConTeXt, most Lua processing is iterating over C data structures using our embedded Lua support libraries. JITting the little bit of Lua code that wraps that together will not help a lot, a few percent at best is my current guess (which is also why incorporating LuaJIT is low priority)

[Tex/LaTex] How to do a ‘printline’ in LuaTeX

If you are using LaTeX (LuaLaTeX), I'd strongly advice against using \directlua{} for more than a simple call to execute another Lua file. \directlua{} is in no way safe. For example:

if you use a Lua comment (--), your code gets Q="!%"§I. This is because in \directlua{} everything is read on one line.
If you try to use a literal % sign, for example in tex.print() you... well, try yourself . Good luck.
If you try to use an active character such as ~ surprising results are guaranteed.
When you want to use tex.print() with a macro, such as \par, you have do crazy stuff to not let TeX see the macro before Lua sees the macro.
And good luck inserting strings like "\n" for a new line character.

Now what to do? Use the environment luacode* from the luacode package:

\begin{luacode*}
  for i=1,3,1 do
    tex.print("FOO\\par")
  end  
\end{luacode*}

If you can't use the luacode package (for example when you use plain TeX), use dofile() or require() to load a package and put your code there. TeX can't find and interpret the code there, only Lua. And then you can write

for i=1,3,1 do
  tex.print("FOO\\par")
end

without trouble.

Best Answer

Related Solutions

[Tex/LaTex] LuaJIT and LuaTeX

[Tex/LaTex] How to do a ‘printline’ in LuaTeX

Related Question