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 10:21:42 +0100 [thread overview]
Message-ID: <7a4b366b-72ea-1d64-ae79-cd3164cf476e@gmx.es> (raw)
In-Reply-To: <84516938-8CAD-4EE3-BE39-94AF518AC692@scorecrow.com>
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 code should read:
\startluacode
-- \\dummycommand
\stopluacode
\starttext
Hello
\stoptext
BTW, in pure Lua:
a = "\a"
b = "\\b"
print(a..b)
outputs "\b".
Sorry, I lack the knowledge to explain this, but backslash seems to be
an special char in pure Lua too.
Just in case it might 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
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-18 9:21 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 [this message]
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
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=7a4b366b-72ea-1d64-ae79-cd3164cf476e@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).