May 2019 - dev-luatex - NTG Mailing Lists

wrong no-file-line-error option
by Hironobu Yamashita 17 Jan '20

17 Jan '20

Hi, The command-line option -no-file-line-error behaves exactly the same as -file-line-error. hironobu$ cat test.tex \x hironobu$ echo x | luatex test This is LuaTeX, Version 1.10.0 (TeX Live 2020/dev) restricted system commands enabled. (./test.tex ! Undefined control sequence. l.1 \x ? warning (pdf backend): no pages of output. Transcript written on test.log. hironobu$ echo x | luatex -file-line-error test This is LuaTeX, Version 1.10.0 (TeX Live 2020/dev) restricted system commands enabled. (./test.tex ./test.tex:1: Undefined control sequence. l.1 \x ? warning (pdf backend): no pages of output. Transcript written on test.log. hironobu$ echo x | luatex -no-file-line-error test This is LuaTeX, Version 1.10.0 (TeX Live 2020/dev) restricted system commands enabled. (./test.tex ./test.tex:1: Undefined control sequence. l.1 \x ? warning (pdf backend): no pages of output. Transcript written on test.log. hironobu$ Best, Hironobu

1 1

Luatex 1.08.0 announcement
by luigi scarso 28 Oct '19

28 Oct '19

============================================================== LuaTeX 1.08 2018-08-28 ============================================================== (1) This release is a prelude to 1.10, the next stable iteration of LuaTeX after version 1.00. (2) Lua 5.3 is now considered to be default and we might use 5.4 in version 1.10. There are no real functional changed expected. You still need to rename the binary for 5.3! (3) Binary mode is no longer available in MPlib but it is still available in stand alone MetaPost. This simplifies compilation and reduces dependencies. (4) The dependency on Poppler for pdf image inclusion has been removed. We now use a small dedicated library written by Pawel Jakowski. We no longer need c++ compilers. We're in the process of making it behave well on all platforms. It has been tested on intel platforms. (5) We know that there can be some (alignment) issues with the arm platform but these are looked into. Therefore, later this year we will release 1.09. Version 1.10 is planned for TeXlive. We hope that ffi works ok on intel and arm platforms at that point. (6) There have been some extensions to the Lua libraries and some callbacks have been added. Also, a few new primitives have been introduced. The documentation mentions the stable extensions. (7) There are the usual bug fixes and cleanups but there have been no real fundamental changes in the API. The LuaTeX team

2 5

[PATCH] Respect find_{output,write}_file result
by Marcel Fabian Krüger 01 Jun '19

01 Jun '19

Hi, according to the documentation find_{output,write}_file should return the name of the to be written file. Currently this is mostly ignored and the original name is always used. Here is a patch to fix this. Best regards, Marcel Krüger --- source/texk/web2c/luatexdir/tex/texfileio.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/texk/web2c/luatexdir/tex/texfileio.c b/source/texk/web2c/luatexdir/tex/texfileio.c index 143e694e1..158757080 100644 --- a/source/texk/web2c/luatexdir/tex/texfileio.c +++ b/source/texk/web2c/luatexdir/tex/texfileio.c @@ -347,7 +347,7 @@ boolean lua_a_open_out(alpha_file * f, char *fn, int n) messaging is left to \LUA\ then. */ - ret = open_outfile(f, fn, FOPEN_W_MODE); + ret = open_outfile(f, str_string(fnam), FOPEN_W_MODE); } } else { if (openoutnameok(fn)) { @@ -379,7 +379,7 @@ boolean lua_b_open_out(alpha_file * f, char *fn) fnam = 0; test = run_callback(callback_id, "S->s", fn, &fnam); if ((test) && (fnam != 0) && (str_length(fnam) > 0)) { - ret = open_outfile(f, fn, FOPEN_WBIN_MODE); + ret = open_outfile(f, str_string(fnam), FOPEN_WBIN_MODE); } } else { if (openoutnameok(fn)) { -- 2.21.0

3 7

[PATCH] Allow literal # in argument text by escaping
by Marcel Fabian Krüger 29 May '19

29 May '19

Hi, inspired by [a recent TeX.sx question][1] this allows delimited macros with `#` in the parameter text by doubling the `#`. It isn't needed that often but it is useful if you try to analyze the parameter text of a TeX macro using TeX code. Also it is completely backward-compatible (`##` always triggers an error without this) and it is very easy to implement. For example: \def\test#1###2{(#1)[#2]} \test hello#{world} would result in (hello)[world] Best regards, Marcel Krüger 1: https://tex.stackexchange.com/questions/491296/can-i-have-a-delimited-macro… --- source/texk/web2c/luatexdir/tex/scanning.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/texk/web2c/luatexdir/tex/scanning.c b/source/texk/web2c/luatexdir/tex/scanning.c index 8f7e1d591..e8b9fca66 100644 --- a/source/texk/web2c/luatexdir/tex/scanning.c +++ b/source/texk/web2c/luatexdir/tex/scanning.c @@ -2095,7 +2095,8 @@ halfword scan_toks(boolean macro_def, boolean xpand) store_new_token(end_match_token); goto DONE; } - if (t == nine_token) { + if (cur_cmd == mac_param_cmd) { + } else if (t == nine_token) { print_err("You already have nine parameters"); help1("I'm going to ignore the # sign you just used."); error(); -- 2.21.0

3 6