From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: Minor bug in Lua or ConTeXt
Date: Wed, 18 Jan 2023 13:41:42 +0000 [thread overview]
Message-ID: <0CE88F52-D82C-476E-98F0-482C66589D1D@scorecrow.com> (raw)
In-Reply-To: <185fecc1-9a4f-d6c3-9196-e399bb2c550e@freedom.nl>
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 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?
Regards,
> On 18 Jan 2023, at 09:48, Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
>
> 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
>> -- \dummycommand
>> \stopluacode
>> \starttext
>> Hello
>> \stoptext
>
> a bang-head-against-the-wall case:
>
> \let\dummycommand\relax
>
> \startluacode
> -- \dummycommand
> \stopluacode
> \starttext
> Hello
> \stoptext
>
> or:
>
> \ifdefined\dummycommand \else \let\dummycommand\relax \fi
>
> a document-on-the-wiki challenge for Pablo
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | 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 / 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
> ___________________________________________________________________________________
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-18 13:41 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 [this message]
2023-01-18 17:47 ` Pablo Rodriguez via ntg-context
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=0CE88F52-D82C-476E-98F0-482C66589D1D@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
/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).