From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Gerben Wierda <gerben.wierda@rna.nl>
Subject: Re: Trying to understand this ctxlua error
Date: Mon, 6 Apr 2020 02:54:01 +0200 [thread overview]
Message-ID: <fb0b7dec-c808-9e53-47c5-b3b0ee17a367@gmail.com> (raw)
In-Reply-To: <2EBF1308-12F4-4EF1-B309-89B403D3FAD6@rna.nl>
Gerben Wierda schrieb am 06.04.2020 um 00:41:
> I got this error after I had changed some lua code:
>
> tex error > tex error on line 272 in file archimate-lua.new: !
> Undefined control sequence
>
> warnIfVerbose( "Breaking off the processing of node %s\nNo
> l...eak
> xsi:type", node)
> \luat_start_lua_code_indeed ...ormalexpanded {\endgroup \noexpand
> \directlua {#1
>
> }}
> l.272 \stopluacode
>
>
>
> <empty file>
>
>
> The control sequence at the end of the top line of your error message
> was never
> \def'ed. You can just continue as I'll forget about whatever was undefined.
>
> I have been looking at that code for over two hours, not seeing anything
> wrong with it. But I’ve now finally found the culprit and I still do not
> get it.
>
> The culprit was:
>
> warnIfVerbose( "Breaking off the processing of %s\n No
> elementRef", node)
>
> The problem goes away when I use:
>
> warnIfVerbose( "Breaking off the processing of %s\nNo
> elementRef", node)
>
> (I don’t want the line after the node is printed to begin with a space).
>
> But the lack of space between \n and N kills lua (apparently). For
> completeness (as string.format and texio.write_nl are also in play):
>
> function warnWithLabelIfVerbose( str, ... )
> if verboseProgram then
> texio.write_nl( str .. string.format(...))
> end
> end
>
> function warnIfVerbose( ... )
> warnWithLabelIfVerbose("-----> ", ...)
> end
>
> Is this a lua bug? A ConTeXt bug? Expected behaviour? And if so, why is
> reported that on line 272 (where \stopluacode is) is the error? Or is
> the error message indeed helpful and do I just lack the know how to
> interpret it?
ConTeXt expands TeX commands in a luacode-environment
and when you have \n followed by text you create a new
command with starts with \n but since it isn't defined
you get a error message.
In the example below the commented block produces
the same error message as you get.
\starttext
%\startluacode
%print("text\ntext")
%\stopluacode
\startluacode
print("text\n text")
\stopluacode
\stoptext
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-04-06 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 22:41 Gerben Wierda
2020-04-06 0:54 ` Wolfgang Schuster [this message]
2020-04-06 9:48 ` Gerben Wierda
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=fb0b7dec-c808-9e53-47c5-b3b0ee17a367@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=gerben.wierda@rna.nl \
--cc=ntg-context@ntg.nl \
/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).