![](https://secure.gravatar.com/avatar/e0f8d84b235b67d60a3c7fd0e326db8d.jpg?s=120&d=mm&r=g)
On 18 Apr 2024, at 01:09, Joel via ntg-context
wrote: ... Or maybe to use > to send the errors to another file for careful study? (using Linux if that matters)
You can run the job from the command line and redirect to a file: $ context file.tex > output.log 2>&1 but that is essentially the same as the .log file that is produced by default when you run from the command line. As your book is large you could try adding \writestatus commands at suitable points so that when your messages appear in the log you know that processing reached that far in the book. Also you could use \writestatus to output messages before and after known problem areas so you can look to see if there is any telltale output in the log and then search for that elsewhere. HTH — Bruce Horrocks Hampshire, UK