From: Hans Hagen <j.hagen@xs4all.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Procházka Lukáš Ing." <LPr@pontex.cz>
Subject: Re: Storing Lua values between Ctx "*first* and next runs
Date: Tue, 17 Jul 2018 17:44:49 +0200 [thread overview]
Message-ID: <4f47b9fd-c15e-91ee-c543-fe16c61c766b@xs4all.nl> (raw)
In-Reply-To: <op.zl43a5ki3h68c7@lkzd-dell-2016>
On 7/14/2018 1:24 PM, Procházka Lukáš Ing. wrote:
> Hello,
>
> is there a Lua variable/namespace which is stored automatically between
> Ctx "*first" and following runs?
>
> I thought 'userdata' is intended for this, but it seems it's not; I'd
> like to achieve something like:
>
> ----
> \startluacode
> if tex.modes["*first"] then
> userdata.LPr = "Something"
> -- Is there a variable which is shared between Ctx runs?
> else
> assert(userdata.LPr == "Something")
> end
> \stopluacode
> ----
>
> Of course, I can store the table via serialization functions to an extra
> file, but I thought there is already a variable/mechanism for this (e.g.
> using .tua/.tuc file) ... is it?
search for datasets in the test suite
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2018-07-17 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 11:24 Procházka Lukáš Ing.
2018-07-17 15:44 ` Hans Hagen [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=4f47b9fd-c15e-91ee-c543-fe16c61c766b@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=LPr@pontex.cz \
--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).