On 1/18/23 19:07, Hans Hagen via ntg-context wrote:
> On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:
> [...]
>> If I’m not wrong (in my previous statement), I think this is
>> counterintuitive, since undefined commands are fine in TeX comments and
>> undefined variables are fine
On 1/18/2023 6:47 PM, Pablo Rodriguez via ntg-context wrote:
from what I understand is that undefined TeX commands cannot be added to
Lua comments.
Indeed. Of course we could have some 'ignore undefined command' feature
but that cripples the engine as well as then also never gives warning in
On 1/18/23 14:41, Bruce Horrocks via ntg-context wrote:
> […]
> Perhaps the Wiki only needs to point out that if you get a Lua
> related error and the error log lists the entire contents of \startluacode ...
> \stopluacode then a possible source of the error is a \command somewhere
> in there?
Thanks Hans.
Before Pablo spends too much effort on the wiki it's worth pointing out that
this only happened because I was in-line documenting the Lua function that I
had written and wanted to name the ConTeXT macro that would invoke it - so it's
trivial for me to avoid this error.
Perhaps
On 1/18/2023 12:36 AM, Bruce Horrocks via ntg-context wrote:
ConTeXt ver: 2023.01.04
The following MWE won't compile because of the \dummycommand line even though
it is a comment. Not sure whether it's a minor bug or an unavoidable aspect of
allowing embedded Lua.
\startluacode
--
On 1/18/23 00:36, Bruce Horrocks via ntg-context wrote:
> ConTeXt ver: 2023.01.04
>
> The following MWE won't compile because of the \dummycommand line
> even though it is a comment. Not sure whether it's a minor bug or an
> unavoidable aspect of allowing embedded Lua.
Hi Bruce,
I think your
ConTeXt ver: 2023.01.04
The following MWE won't compile because of the \dummycommand line even though
it is a comment. Not sure whether it's a minor bug or an unavoidable aspect of
allowing embedded Lua.
\startluacode
-- \dummycommand
\stopluacode
\starttext
Hello
\stoptext
—
Bruce Horrocks
