From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: printing tab in lua: print('a\tb') fails
Date: Thu, 27 Nov 2008 11:17:10 +0100 [thread overview]
Message-ID: <115224fb0811270217l22b82206o2f2ff9ce61aa96bc@mail.gmail.com> (raw)
In-Reply-To: <115224fb0811270102g102c4bbfpd80b0d7e54f7165c@mail.gmail.com>
On Thu, Nov 27, 2008 at 10:02 AM, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
> On Thu, Nov 27, 2008 at 9:42 AM, luigi scarso <luigi.scarso@gmail.com> wrote:
>>
>>
>>>
>>> OK, I will use external files next time. In this quick-and-dirty
>>> approach I just added string.format since it was easier than
>>> restructuring everything.
>>>
>>> I thought that \startluacode should be behaving the same way as
>>> verbatim environments where commands inside verbatim have no
>>> influence, but apparently I was wrong.
>>
>> I also think so.
>> Can be strange, but inside a \startluacode\stopluacode I have no problems to
>> think at -- as comment
>> while I have problems to think to % as comment
>>
>> And put lua code in a separate file not always is a good solution
>
> This would be really great, \start/stoplua with % for comments like \ctxlua
> and \start/stopluacode with -- as comment, the first is used for longer settings
> in macros and the second for inline functions.
>
> @Luigi: You could try to parse the luacode content with Lpeg and with
> the result back to \directlua.
Correction:
-- works as comments in luacode
% is used to format strings
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-11-27 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 19:07 Mojca Miklavec
2008-11-26 19:28 ` Wolfgang Schuster
2008-11-27 8:29 ` Mojca Miklavec
2008-11-27 8:42 ` luigi scarso
2008-11-27 9:02 ` Wolfgang Schuster
2008-11-27 9:28 ` luigi scarso
2008-11-27 10:17 ` Wolfgang Schuster [this message]
2008-11-27 11:48 ` luigi scarso
2008-11-27 12:03 ` Hans Hagen
2008-11-27 13:00 ` luigi scarso
2008-11-27 8:50 ` Wolfgang Schuster
2008-11-27 10:04 ` Hans Hagen
2008-11-27 8:13 ` 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=115224fb0811270217l22b82206o2f2ff9ce61aa96bc@mail.gmail.com \
--to=schuster.wolfgang@googlemail.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).