From: Hans Hagen <j.hagen@xs4all.nl>
To: Tomas Hala <tomas.hala@mendelu.cz>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Parsing \...luacode within a \def
Date: Thu, 14 Jun 2018 21:41:28 +0200 [thread overview]
Message-ID: <125d2d61-e457-b514-b2eb-516d38884e1c@xs4all.nl> (raw)
In-Reply-To: <20180614191834.GA25201@akela.mendelu.cz>
On 6/14/2018 9:20 PM, Tomas Hala wrote:
> Hi Lukáš,
>
> I am not sure but I guess that the problem is related with the behaviour of
> the input processor which erases characters at the end of line (CR, LF) and
> replace them by a space. Then, the whole content between \start/stopluacode
> is at only one line. If you the second way of comment marks, the letter "u"
> will be shown at the output.
>
> Tomáš
>
> \def\U{%
> \startluacode
> --[[ blahblah
> ]]--
>
> context("u")
> \stopluacode
> }
indeed, \startluacode inside a macro body acts like any such catcode
regime changing operation ..
\def\foo{%
f%oo
}
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 / 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:[~2018-06-14 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:48 Procházka Lukáš Ing.
2018-06-14 19:20 ` Tomas Hala
2018-06-14 19:41 ` Hans Hagen [this message]
2018-06-18 7:53 ` Procházka Lukáš Ing.
2018-06-14 18:52 Procházka Lukáš Ing.
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=125d2d61-e457-b514-b2eb-516d38884e1c@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=tomas.hala@mendelu.cz \
/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).