ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Minor bug in Lua or ConTeXt
Date: Wed, 18 Jan 2023 18:47:33 +0100	[thread overview]
Message-ID: <d9647ae6-ee17-979b-c08c-73c1dc99d2bc@gmx.es> (raw)
In-Reply-To: <0CE88F52-D82C-476E-98F0-482C66589D1D@scorecrow.com>

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?

Hi Bruce,

from what I understand is that undefined TeX commands cannot be added to
Lua comments.

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 inside \startluacode … \stopluacode.

So I added
https://wiki.contextgarden.net/Programming_in_LuaTeX#Undefined_Commands_in_Lua_Comments.

Let me know whether I missed something.

Many thanks for your help,

Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2023-01-18 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 23:36 Bruce Horrocks via ntg-context
2023-01-18  9:21 ` Pablo Rodriguez via ntg-context
2023-01-18  9:48 ` Hans Hagen via ntg-context
2023-01-18 13:41   ` Bruce Horrocks via ntg-context
2023-01-18 17:47     ` Pablo Rodriguez via ntg-context [this message]
2023-01-18 18:07       ` Hans Hagen via ntg-context
2023-01-18 18:25         ` Pablo Rodriguez via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9647ae6-ee17-979b-c08c-73c1dc99d2bc@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).