Re: [NTG-context] What to do when ConTeXt not revealing the error details?

2022-10-30 Thread Aditya Mahajan via ntg-context
On Mon, 31 Oct 2022, Joel via ntg-context wrote: > I found what it was, a % in the text preventing a \stopitemize to close a > list. Thanks! --Joel mtxrun concheck filename is very useful in such situations. Aditya

Re: [NTG-context] What to do when ConTeXt not revealing the error details?

2022-10-30 Thread Joel via ntg-context
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 wrote: Hi Joel, I get this error frequently when I forget to stop an environment, for example a \startsection with no \stopsection or

Re: [NTG-context] What to do when ConTeXt not revealing the error details?

2022-10-30 Thread Gavin via ntg-context
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

[NTG-context] What to do when ConTeXt not revealing the error details?

2022-10-30 Thread Joel via ntg-context
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