[lltx] quietening lualatex console output

Philipp Stephani st_philipp at yahoo.de
Sat Jan 29 11:57:21 CET 2011


Please stay on the list!

Am 29.01.2011 um 11:15 schrieb Arno Trautmann:

> Philipp Stephani wrote:
>> Am 29.01.2011 um 05:04 schrieb Will Robertson:
>>> Hi,
>>> 
>>> When I run a unicode-math document with LuaLaTeX, here's the console output I get purely related to loading the various Lua stuff:
>>> 
>>> (/usr/local/texlive/2010/texmf-dist/tex/luatex/luaotfload/luaotfload.sty
>>> […]
>>> 
>>> Is there any way to make this quieter? (Can lua files be loaded from lua without being printed in the console output?)
>> 
>> I think LuaTeX should aim for more sane output in general, similar to other non-TeX compilers. That means:
>> - No printing of page numbers (already possible), file names (suggested in http://tracker.luatex.org/view.php?id=535) and similar nonsense. People who are interested in which files are loaded can use the filename recorder.
>> - All messages use file:line:message style, even those that come from \write or Lua print() or texio.write()
>> - \scrollmode (i.e. no user interaction) by default
>> - Primitives or Lua functions for printing errors, warnings and informational messages
>> - Getting rid of \errhelp
>> - Messages are never broken across lines; every message is exactly one line; newline chars in messages are converted to spaces
>> - No continuation of messages
>> - No log file
> 
> What is wrong with the log file? It does not disturb anything as it does
> not show up in the user interface, but is usefull. What will be gained
> by no log?

One file less in the already over-crowded output directory. I must admit that the log file is probably the weakest point on my list; it might still be helpful for debugging purposes. But I still think that no log file should be the rule rather than the exception since GCC and other compilers don't produce log files either.



More information about the lualatex-dev mailing list