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 ___________________________________________________________________________________
