From: Rudolf Bahr <quasi@quasi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Exchangeing content of variables between luacode and context
Date: Wed, 20 Nov 2019 17:57:38 +0100 [thread overview]
Message-ID: <20191120165738.GA30651@nan> (raw)
In-Reply-To: <d22c68d0-4b0a-4bb0-dfca-3f9dd548d3de@xs4all.nl>
On Wed, Nov 20, 2019 at 09:24:44AM +0100, Hans Hagen wrote:
> you can store info in the tuc file (there are examplex on the wiki and in
> the test suite) or you cam create a table, save it at the end of the run and
> load it at the start
>
> (assuming that you cannot just recalculate the values each run, but i assume
> that you have a reason for not doing that)
Hraban and Hans, I thank you for your answers!
Recalculating the results of invoked Luacode functions might be the best
and simplest choice, because finding a good hash key for a lua table which
must be created by the ConTeXt/Luacode program page itself could become rather
difficult (one could get into devil's kitchen, as we say). On the other side
one single lua table only for the current run, similar to .tuc files, is helpful
and necessary to have a look onto the results of the used luacode functions.
Sometimes they are the only help in error finding.
Rudolf
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2019-11-20 16:57 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
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 [this message]
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=20191120165738.GA30651@nan \
--to=quasi@quasi.de \
--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).