- dev-luatex - NTG Mailing Lists

Proposal for new primitives
by Marcel Krüger 03 May '18

03 May '18

Hi, i want to propose two new primitives for LuaTeX: - The existing `\luafunction` has some similarities to `\count`, `\dimen`, `\skip`. Especially for most use cases, you will have to allocate a number, but there is no equivalent to `\countdef` etc. I think LuaTeX would benefit from `\luafunctiondef`, such that e.g. `\luafunctiondef\something1` would define `\something`, such that `\something` is equivalent to `\luafunction1`. What is the difference to creating a regular macro? This would allow `\something` to be expandable in a single step, which is especially important for emulating primitives from other engines with lua code. - Additionally it would be useful to allow "expandable temporary macro definitions". So for example \scantexmacro#1#2\stop{-#1-#2-}abc\stop def would expand to -a-bc-def This allows using the TeX macro argument parser inside expandable macros, especially when the delimiter can change. For example if you implement a property list as `\@key key1\@value value1\@key key2\@value value2...`, you can create an expandable macro to ge the value of key `#2` without requiring recursive calls with \def\propget#1#2{% \scantexmacro##1\@key#2\@value##2\@key##3\stop{% ##2% }#1\@key#2\@value\@key\stop } Another use-case would be implementingan expandable version of functionality similar to the expl3 `\seq_map_inline:Nn`. What do think? Is there any chance to see something like this in LuaTeX? I attached a first implementation as patch against the current experimental branch. Best regards Marcel Krüger

2 1

\primitive for non-primitive
by Hironobu Yamashita 28 Apr '18

28 Apr '18

Hi, LuaTeX raises "Missing primitive name" error for the following: \primitive\NONE \end PDFTeX (\pdfprimitive) and XeTeX (\primitive) simply ignores non-primitive, as the PDFTeX manual says > This command executes the primitive meaning of the following control sequence, > regardless of whether the control sequence has been redefined or made undefined. > If the primitive was expandable, \pdfprimitive expands also. > On the other hand, if the following control sequence never was a primitive, > nothing happens and no error is raised. > (In some versions of pdfTEX prior to 1.40.19, an error was wrongly given.) Hironobu Yamashita

2 3

Luatex 1.07.0 announcement
by luigi scarso 19 Apr '18

19 Apr '18

============================================================== LuaTeX 1.07 2018-01-17 ============================================================== (1) This release brings Lua 5.3 to LuaTeX. We have tested an experimental version for a few months and not encountered issues. (2) If you use Lua 5.3 you should be aware of a few changes in the language and its implementation. Numbers are now either integers or floats but are cast automatically. (3) In some cases (e.g. string.format) there is a more strict check. A float always has a decimal appended when serialized, so 1 becomes 1.0 as string. (4) We keep supporting the bit32 library on top of the new bit operators. Be aware of the fact that currently LuajitTeX does not have these operators. (5) Performance of LuaTeX with Lua 5.3 can be slightly better than with 5.2 but this really depends on your usage of Lua. In practice there should be no slowdown. (6) We are aware of possible substantial slowdown of string.format depending on the platform and compiler. This depends on Lua too and will be resolved in due time. (7) If you want to test with Lua 5.3 then have to build LuaTeX with --lua53. Because ConTeXt will switch to 5.3 after this release there will be binaries available at the ConTeXt garden. (8) The 2018 TeXlive distribution will ship with LuaTeX using Lua 5.2 but there will likely be an additional binary LuaTeX53 available. (9) From 2019 TeXlive will ship with LuaTeX and Lua 5.3 as default. We provide --lua52 as build flag for a while. By then we might be looking at Lua 5.4 already. (10) There are the usual patches and cleanups and a few small additions (mentioned in the manual) but there have been no fundamental changes in the API (apart from removing depricated and undocumented functionality). The LuaTeX team

1 0

openin_any = p in texmf.cnf
by Reinhard Kotucha 18 Mar '18

18 Mar '18

excerpt from texmf.cnf: ------------------------------------------------------------------------- % Do we allow TeX \input or \openin (openin_any), or \openout % (openout_any) on filenames starting with `.' (e.g., .rhosts) or % outside the current tree (e.g., /etc/passwd)? % a (any) : any file can be opened. % r (restricted) : disallow opening dot files % p (paranoid) : as `r' and disallow going to parent directories, and % restrict absolute paths to be under $TEXMFOUTPUT. openin_any = a ------------------------------------------------------------------------- Dear Sirs, when I set openin_any = p then fmtutil can't create any LuaTeX-based format files anymore: $ fmtutil --sys --all [...stuff omitted...] fmtutil [ERROR]: running `luatex -ini -jobname=luatex -progname=luatex luatex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running `luajittex -ini -jobname=luajittex -progname=luajittex luatex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running `luatex -ini -jobname=lualatex -progname=lualatex lualatex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running `luatex -ini -jobname=dvilualatex -progname=dvilualatex dvilualatex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running `luatex -ini -jobname=pdfcsplain -progname=pdfcsplain -etex csplain.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict fmtutil [ERROR]: running `luatex -ini -jobname=dviluatex -progname=dviluatex dviluatex.ini </dev/null' return status 1 fmtutil [ERROR]: return error due to options --strict Only LuaTeX-based formats are concerned, all other format files are built successfully. Everything works as expected with openin_any = a and openin_any = r I'm using the latest stuff in tlpretest. Regards, Reinhard -- ------------------------------------------------------------------ Reinhard Kotucha Phone: +49-511-3373112 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ------------------------------------------------------------------

3 3

Semi-official git mirror of luatex repository
by Mojca Miklavec 13 Mar '18

13 Mar '18

Hi, I would be super grateful if there was a semi-official git mirror of the luatex repository that would also be updated via regular (hourly?) cron jobs. Henri would like to set up some Travis builders for testing LuaTeX builds as part of the effort to get better support for musl. There are some existing clones, some better than the others, some updated less frequently than the others. Does anyone volunteer to create a nice clone with regular updates, proper author map and some reasonable branch/tags setup? (Having it perfect is not really required, but it would be super nice to have a nice regularly updated clone.) Thank you very much, Mojca

2 2

Unknown command "mv -v" on Solaris
by Mojca Miklavec 07 Mar '18

07 Mar '18

Hi, LuaTeX build fails on Solaris due to "mv -v" in build.sh: if [ "$BUILDLUA52" = "FALSE" ] && [ "$BUILDLUA53" = "TRUE" ] then mv -v "$B"/texk/web2c/$LUATEXEXE53 "$B"/texk/web2c/$LUATEXEXE ls -l "$B"/texk/web2c/$LUATEXEXE fi mv: illegal option -- v Usage: mv [-f] [-i] f1 f2 mv [-f] [-i] f1 ... fn d1 mv [-f] [-i] d1 d2 build/texk/web2c/luatex: No such file or directory Can you please perhaps store the command and echo it before executing it instead of calling "mv -v" which is apparently not portable enough? Thank you, Mojca

2 1

variable
by and＠linux.pl 06 Mar '18

06 Mar '18

Hello, Anybody know how I can set variable in tex? For example \count10=20 \def\proste{To jest prosty napis} a\directlua{tex.print(tex.count[10]+5)}b a\directlua{tex.set("\proste","Trudne")}b \proste \bye I need setup \proste definition to my own string How I can read TeX variable \mynumber from lua and set variable \mynumber on TeX but set in lua script. Thanks Janusz Biznesu

3 4

source code of LuaTeX
by Patrick Gundlach 03 Oct '17

03 Oct '17

Hi all, where can I get the source code of LuaTeX? The link on the web page (http://www.luatex.org/download.html) is protected with a username/password. The page https://foundry.supelec.fr/scm/?group_id=10 does not exist anymore? Any other source? Patrick

4 3

Problems caused in Lua programs by setting LC_{CTYPE, COLLATE, NUMERIC} to C
by Reuben Thomas 20 Sep '17

20 Sep '17

Today I noticed that my Compose key did not seem to be working in my PDF viewer (Evince on GNOME). On investigation, this turned out to be a problem with the texdoc command, and specifically, that texlua changes the environment variables LC_CTYPE, LC_COLLATE and LC_NUMERIC. In this particular case, I think running a more recent version of LuaTeX would suffice (I have 0.80), as texdoc tries to reset LC_CTYPE before running external commands (and it turns out that this is the setting that causes my problem), but a comment in the current (version 2.017) version of texdoc says: In older versions of luatex, status.lc_* will be nil. For now, I've simply patched texdoc to set LC_CTYPE to the empty string. However, this sort of problem could still occur with functionality of programs started by texdoc that relies on LC_COLLATE or LC_NUMERIC, and further, it can affect any program run with texlua that starts other external programs or uses locale-dependent functionality. Therefore, I wonder whether it would be possible to have an easy way to undo or prevent this environment change? The most obvious way would be not to change the environment when the executable is run as "texlua". Relatedly, I have a bug fix for texdoc; is this the right place to send it? -- https://rrt.sc3d.org

1 0

Change of "--recorder" behaviour
by Hoffmann, Jobst 06 Sep '17

06 Sep '17

With LuaTeX, Version 0.95.0 (TeX Live 2016) the .fls file contains lines like INPUT llatex.tex INPUT ./llatex.txt where the two files were input by Lua code (io.open, io.lines), not by standard LaTeX code like \input. These lines are missing with LuaTeX,Version 1.0.4 (TeX Live 2017). Is that behaviour intended? Is there a workaround to get these lines back (they are needed for latexmk)? Can I override the function to get back the old behaviour? If it is needed, I can provide a MWE. Thanks in advance Jobst

1 0