On 4/13/22 00:27, Bruce Horrocks via ntg-context wrote:
>> On 12 Apr 2022, at 18:14, Pablo Rodriguez via ntg-context
>> wrote:
>>
>> I wonder whether it would be possible that ConTeXt or LuaMeTaTeX could
>> be more verbose about an opened environment that isn’t closed.
>
> $ mtxrun --script check
On 4/12/22 20:04, Otared Kavian via ntg-context wrote:
> Hi Pablo,
>
> Your example works fine on my machine (MacOS 11.6.4) with LMTX
> version 2022.04.11.
Hi Otared,
many thanks for your reply.
The fatal error prevents an extra run, but it doesn’t prevent the PDF
generation.
In my original docu
> On 12 Apr 2022, at 18:14, Pablo Rodriguez via ntg-context
> wrote:
>
> I wonder whether it would be possible that ConTeXt or LuaMeTaTeX could
> be more verbose about an opened environment that isn’t closed.
$ mtxrun --script check filename.tex
is something I learned from this list.
—
Br
2 20:05
> An: mailing list for ConTeXt users
> Cc: Otared Kavian
> Betreff: Re: [NTG-context] fatal error in LMTX
>
> Hi Pablo,
>
> Your example works fine on my machine (MacOS 11.6.4) with LMTX version
> 2022.04.11. However in your example the \stopfrontmatter is missing.
&g
Hi Pablo,
Your example works fine on my machine (MacOS 11.6.4) with LMTX version
2022.04.11. However in your example the \stopfrontmatter is missing.
Best regards: Otared
> On 12 Apr 2022, at 19:14, Pablo Rodriguez via ntg-context
> wrote:
>
> Hi Hans,
>
> I have a minimal sample that trigg
Hi Hans,
I have a minimal sample that triggers a fatal error in ConTeXt LMTX
(current latest from 2022.04.11 19:27):
\starttext
\startfrontmatter
\input zapf
\stoptext
This gives the following error message:
mkiv lua stats > runtime: 0.386 seconds, 1 processed pages,
1 shipped pa
