From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rudolf Bahr <quasi@quasi.de>
Subject: Re: Exchangeing content of variables between luacode and context
Date: Tue, 19 Nov 2019 16:55:15 +0100 [thread overview]
Message-ID: <cecb89c1-e2a0-2bad-3a2c-272aa8f9e909@gmail.com> (raw)
In-Reply-To: <20191119131942.GA6059@nan>
Rudolf Bahr schrieb am 19.11.2019 um 14:19:
> Hello All!
>
> To send variable contents from context to luacode I can put them into the
> function invocation or use 'tokens.getters.macro("TestA")',
> an interesting and very nice possibility to let luacode itself getting
> contents of context macros. The (only?) way back, from luacode to context,
> could be done by 'tokens.setters.macro("TestA","a")' [1] .
>
> Now, to store Luacode's variable contents permanently in context programs
> I could Luacode let copy my ConTeXt program to another place on disk with
> a newly defined macro inside. But, does somebody know (by chance) of another,
> more elegant possibility? I think giving back a value by "return" won't work.
Can you make a minimal example of your actual problem.
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-11-19 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 13:19 Rudolf Bahr
2019-11-19 15:55 ` Wolfgang Schuster [this message]
2019-11-19 19:34 ` Rudolf Bahr
2019-11-20 6:43 ` Henning Hraban Ramm
2019-11-20 8:24 ` Hans Hagen
2019-11-20 16:57 ` Rudolf Bahr
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=cecb89c1-e2a0-2bad-3a2c-272aa8f9e909@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=quasi@quasi.de \
/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).