[XeTeX] Overfull boxes return status of 0 in XeTeX

Wilfred van Rooijen wvanrooijen at yahoo.com
Sun Mar 13 15:43:55 CET 2016

It seems that the source code from TeXworks is available, so it should be possible to add a feature to "turn overfull boxes into some sort of error but not quite". You'd have to talk to the TeXworks people. 

On a linux computer, you could implement your own request by making an alias: make an executable file called "xelatex" and add it to the search path before the latex path; then, this new "xelatex" is really a script (shell script, or python, can be anything) which calls xelatex (with the absolute path to avoid confusion). When the xelatex run finishes, the script inspects the log file and provides a non-zero exit status on certain errors and warnings.


    On Sunday, March 13, 2016 11:32 PM, Philip Taylor <P.Taylor at Rhul.Ac.Uk> wrote:


Wilfred van Rooijen wrote:

> Anyway, isn't there some kind of setting in TeXworks for this?

Not at the moment.

> Or is there perhaps a command line option for latex "turn warnings
> into errors", like with gcc?

Also not at the moment, but that is essentially what I am requesting,
except that I don't want warnings to be treated as /full/ errors
(thereby pausing the compilation and demanding user input) but rather to
simply return a non-zero status (if that what the user wants) that can
then be interpreted by an intelligent wrapper such as TeXworks.  My
suggestion is :

    *TeX --return-non-zero-status-on=<set of keywords>

(where *TeX implies any of eTeX, PdfTeX, XeTeX, etc., and <keywords>
might include "overfull-boxes", "missing-glyphs", etc.)

** Phil.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/xetex/attachments/20160313/afff7386/attachment.html>

More information about the XeTeX mailing list