From: Gerben Wierda <gerben.wierda@rna.nl>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Trying to understand this ctxlua error
Date: Mon, 6 Apr 2020 11:48:03 +0200 [thread overview]
Message-ID: <8060B154-2C22-41CB-ABDC-50FFC82E238C@rna.nl> (raw)
In-Reply-To: <fb0b7dec-c808-9e53-47c5-b3b0ee17a367@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2961 bytes --]
On 6 Apr 2020, at 02:54, Wolfgang Schuster <wolfgang.schuster.lists@gmail.com> wrote:
>
> 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
OK, thanks. This means the ConTeXt environment mixes standard TeX (where \nfoo would be considered a TeX command) and lua string substitution (where \nfoo would mean a newline followed by foo), correct? I understand why that happens (otherwise one would have to escape all \ characters directed at TeX) but it really took me hours (because I did not understand the error message that correctly told me \Nno was the problem). It’s what you see depends on what you are looking for, I guess.
Maybe a warning in the documentation (or maybe there is one and I missed it)
G
[-- Attachment #1.2: Type: text/html, Size: 17671 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-06 9:48 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
2020-04-06 9:48 ` Gerben Wierda [this message]
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=8060B154-2C22-41CB-ABDC-50FFC82E238C@rna.nl \
--to=gerben.wierda@rna.nl \
--cc=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.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).