From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Lua conditionals fail inside \starttexdefinition
Date: Tue, 4 Sep 2012 14:21:09 +0200 [thread overview]
Message-ID: <20120904142109.32f088b2@homerow> (raw)
Hi,
I discovered strange behaviour concerning Lua conditionals within
texdefinitions.
ConTeXt complains: 'then' expected near 'thenelseend'.
I guess it has something to do with how the content of a
texdefinitions is grabbed. Seems like a bug or is this by design?
% This works fine
\def\mycmd{%
\startluacode
if true then
else
end
\stopluacode}
% This one fails
% \starttexdefinition mycmd
% \startluacode
% if true then
% else
% end
% \stopluacode
% \stoptexdefinition
\startluacode
userdata = userdata or { }
function userdata.myfun()
if true then
else
end
end
\stopluacode
% This also works fine
\starttexdefinition mycmd
\luacode{userdata.myfun()}
\stoptexdefinition
\mycmd
Marco
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2012-09-04 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 12:21 Marco Patzer [this message]
2012-09-04 12:26 ` Wolfgang Schuster
2012-09-04 18:24 ` Aditya Mahajan
2012-09-04 18:34 ` Wolfgang Schuster
2012-09-04 18:44 ` Marco Patzer
2012-09-04 18:56 ` Herbert Voss
2012-09-04 19:05 ` Marco Patzer
2012-09-04 19:15 ` luigi scarso
2012-09-04 19:18 ` Herbert Voss
2012-09-04 19:35 ` Marco Patzer
2012-09-04 19:39 ` Herbert Voss
2012-09-04 19:47 ` Marco Patzer
2012-09-04 19:41 ` luigi scarso
2012-09-04 19:05 ` Aditya Mahajan
2012-09-04 19:22 ` luigi scarso
2012-09-04 19:28 ` Herbert Voss
2012-09-05 9:09 ` Hans Hagen
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=20120904142109.32f088b2@homerow \
--to=homerow@lavabit.com \
--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).