Zdenek Wagner wrote:
> In the very same way as TeX is called. It has to start a shell (cmd.exe > in Windows) and ask it to start the lua interpreter and execute the lua > script. If you want to analyze the log file immediatelly, I would write > a lua script that would run tex, then looked into the log file and then > generate an output and/or status code for the front end. The script > would know the TeX command and the file name, hence it would know the > name of the log file. You can invent command lines parameters for the > script itself so that you can ask it to extract various pieces of > information from the log to the console. One of my scripts extracts > information on all overful \hboxes and the underful \hbox with the > greatest badness. Well, the TeXworks list has been copied into most (but not all) of this thread, so I think it better if I allow Stefan to respond for himself. My belief remains unchanged -- it is the engines that should be enhanced, rather than the front ends, but in such a way that their current behaviour is unaltered (e.g., a new command-line parameter). ** Phil. -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
