Same with W64 on W11. On 2021-12-24 17:08, Jairo A. del Rio via ntg-context wrote:

Hi, Hans. In Ubuntu 20.04:

resolvers       > lua > loading file '/home/coragyps/lmtx/tex/texmf-context/tex/context/base/mkxl/node-cmp.lmt' succeeded

fatal error: storage cannot be marked

Jairo

El vie, 24 dic 2021 a la(s) 13:45, Hans Hagen via ntg-context (ntg-context@ntg.nl) escribió:

Hi,

When wrapping up before the weekend I uploaded a new lmtx (bottom floats fixed afaiks, but hat mechanism might see some improvements anyway next year; exit codes more reliable; some low level tracing; side float coming loose from section head issue solved; ...).

I'm experimenting with some more efficient low level state info and in the process ran into an issue / interference with (also low level) attributes. I'm not sure if I solved it (work in progress, i need to run into another border case first which may take ages) but the test suite runs ok so ...

Hans

-----------------------------------------------------------------                                            Hans Hagen | PRAGMA ADE                Ridderstraat 27 | 8061 GH Hasselt | The Netherlands         tel: 038 477 53 69 | www.pragma-ade.nl http://www.pragma-ade.nl | www.pragma-pod.nl http://www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage  : http://www.pragma-ade.nl / http://context.aanhet.net archive  : https://bitbucket.org/phg/context-mirror/commits/ wiki     : http://contextgarden.net ___________________________________________________________________________________

___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist :ntg-context@ntg.nl /http://www.ntg.nl/mailman/listinfo/ntg-context webpage :http://www.pragma-ade.nl /http://context.aanhet.net archive :https://bitbucket.org/phg/context-mirror/commits/ wiki :http://contextgarden.net ___________________________________________________________________________________

On Sat, 25 Dec 2021 11:55:31 +0100 Hans Hagen wrote:

...

mtxrun --autogenerate --script context --autopdf "oeps.tex"

....

mkiv lua stats > runtime: 0.485 seconds, 1 processed pages, 1 shipped pages, 2.062 pages/second mtx-context | fatal error: return code: 1

so ... an error ... that's the most i can do

I did some more checking. It seems to return 1 on *some* errors, but not on all the ones supported by --errors. This example e.g. compiles with return code 0: %% enables logging of errors \enabledirectives [logs.errors] %% missing font \definefontfamily [foo] [serif] [no font here really] \setupbodyfont [foo] \starttext %% missing characters 𝒜 %% missing figure \externalfigure [foo] %% missing references See \in{section}[sec:none]. \stoptext Marco

On Sat, 25 Dec 2021 12:44:31 +0100 Hans Hagen wrote:

because these are not errors in the sense of 'quit' ... for instance missing references can be resolved in a second run

Ok, but that's what the context runner is for, not? It's smart and knows when it's hitting the last run and if there are still unresolved issues, it could then report the correct return value to the environment. The runner is responsible for the final return value, not the individual context run AFAIK.

you need to be explicit:

\enabledirectives [logs.errors={missing references,missing characters}]

Ok, that works, great news. So if I understand you correctly, there's no command to enable them *all* at once? Frankly, I'd expect \enabledirectives [logs.errors] to enable them all (including the correct return value), but apparently it only enables the reporting and doesn't affect the return value. That begs the question: Which error directives are available (so I can manually enable them)? Side note: A missing font is not an error: \enabledirectives [logs.errors] \definefontfamily [foo] [serif] [no font here really] \setupbodyfont [foo] \starttext foo \stoptext But I guess that's just not supported. Marco