What to do when ConTeXt not revealing the error details?
I have a very large document that, when compiled, produces a PDF, but reports the error "mtx-context | fatal error: return code: 1". The PDF can open, but after about 100 pages in, the content starts appearing all in the wrong place. Usually when I compile, it says there is an error, and I just scroll up until I find the details. I've scrolled through the output, and *.log file, but cannot see anything that looks like an error. It could be that just because the document is so long (about 1200 pages), I can't find the error among the huge logs, but I looked through them all carefully. How can I isolate the error when ConTeXt isn't showing it? Is there some setting for showing only errors, or revealing more details about an error? --Joel
Hi Joel, I get this error frequently when I forget to stop an environment, for example a \startsection with no \stopsection or a \startplacefigure with no \stopplacefigure. This freqeuntly doesn’t cause an error because the engine is happily packing my entire book into a margin figure. See if there something you should have stopped near the place where things go bad? Good luck! Gavin
On Oct 30, 2022, at 7:46 PM, Joel via ntg-context
wrote: I have a very large document that, when compiled, produces a PDF, but reports the error "mtx-context | fatal error: return code: 1".
The PDF can open, but after about 100 pages in, the content starts appearing all in the wrong place.
Usually when I compile, it says there is an error, and I just scroll up until I find the details. I've scrolled through the output, and *.log file, but cannot see anything that looks like an error.
It could be that just because the document is so long (about 1200 pages), I can't find the error among the huge logs, but I looked through them all carefully.
How can I isolate the error when ConTeXt isn't showing it? Is there some setting for showing only errors, or revealing more details about an error?
--Joel ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________
I found what it was, a % in the text preventing a \stopitemize to close a list. Thanks! --Joel
On Sunday, October 30, 2022 at 07:56:44 PM MDT, Gavin
On Oct 30, 2022, at 7:46 PM, Joel via ntg-context
wrote: I have a very large document that, when compiled, produces a PDF, but reports the error "mtx-context | fatal error: return code: 1".
The PDF can open, but after about 100 pages in, the content starts appearing all in the wrong place.
Usually when I compile, it says there is an error, and I just scroll up until I find the details. I've scrolled through the output, and *.log file, but cannot see anything that looks like an error.
It could be that just because the document is so long (about 1200 pages), I can't find the error among the huge logs, but I looked through them all carefully.
How can I isolate the error when ConTeXt isn't showing it? Is there some setting for showing only errors, or revealing more details about an error?
--Joel ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________
participants (3)
-
Aditya Mahajan
-
Gavin
-
Joel