From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How well do ConTeXt (lua)module for other users?
Date: Tue, 19 Jul 2011 16:26:02 +0200 [thread overview]
Message-ID: <4E2593FA.8040401@gyza.cz> (raw)
In-Reply-To: <536E46DE-9395-4096-AA6E-D405ACE51A1A@googlemail.com>
Great ... that's exactly what I needed ... Thanks very much Wolfgang.
It can be somewhere on similar techniques to read more? Just links to
some sample files to the dissected ...
Thanks a lot
Jaroslav
Dne 19.7.2011 14:39, Wolfgang Schuster napsal(a):
> Am 19.07.2011 um 14:27 schrieb Jaroslav Hajtmar:
>
>
>> > Hello ConTeXist.
>> >
>> > I have done the module (for context), which is entirely written in Lua (ConTeXt definitions are done through Lua too).
>> >
>> > I wonder how it can be loaded into ConTeXt file. Have I to use the beginning of the file:
>> > \startluacode
>> > dofile ("my-module.lua")
>> > \stopluacode
>> >
>> > to loading the module? I would like to use \usemodule [my-module.lua], but there is a problem, that code must be inside \startluacode ... \stopluacode environment.
>> > But when I put my luacode into \startluacode ... \stopluacode into my-module.mkiv file, then I have a problem with catcodes inside strings defining by [[ ... ]].
>> >
>> > Or must be module consists of two separate files (my-module.lua and my-module.mkiv)? Must I to load the Lua module file (my-module.lua) into ConTeXt module file (my-module.mkiv) by command \ctxlua{dofile("my-module.lua ");} and then load module file (my-module.mkiv) into my user file by command \usemodule[my-module]?
>> >
>> > Is there something like \useluamodule[....] or \usemodule[anyluaswitch][modulefile] ???
>> >
>> > How to proceed in these cases? I find it inappropriate to divide the module into two separate files.
>>
> Use \usemodule:
>
> <example>
> \startbuffer[test]
> function test(argument)
> context.quotation(argument)
> end
>
> interfaces.definecommand {
> name = "test",
> arguments = {
> { "content", "string" },
> },
> macro = test,
> }
> \stopbuffer
>
> \savebuffer[test][p-test.lua]
>
> \usemodule[test]
>
> \starttext
> \test{Hello}
> \stoptext
> </example>
>
> 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-07-19 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 12:27 Jaroslav Hajtmar
2011-07-19 12:31 ` luigi scarso
2011-07-19 12:39 ` Wolfgang Schuster
2011-07-19 14:26 ` Jaroslav Hajtmar [this message]
2011-07-19 15:06 ` Wolfgang Schuster
2011-07-20 7:40 ` Jaroslav Hajtmar
2011-07-20 9:41 ` 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=4E2593FA.8040401@gyza.cz \
--to=hajtmar@gyza.cz \
--cc=ntg-context@ntg.nl \
--cc=schuster.wolfgang@googlemail.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).