From: Andreas Schneider <aksdb@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Howto use the lua io.read() function only in the first context run?
Date: Thu, 17 Mar 2016 09:11:12 +0100 [thread overview]
Message-ID: <42a53307693b3de32917ff53aef43cff@chemnitz.dyndns.aksdb.de> (raw)
In-Reply-To: <20160316214757.GA26276@nereid.neptune>
Am 2016-03-16 22:47, schrieb Romain Diss:
> Hi,
>
> Thank you Hans... but it doesn't fully work. Now I only enter the input
> once (that's ok) but on the second run, the variable is not defined
> anymore. How can I keep it in the conTeXt memory?
>
> -- Minimum still not working example
> local name
> if environment.arguments.currentrun == "1" then io.read() end
> context.startdocument()
> context("Hello " .. name)
> context.stopdocument()
>
> All the best
You can use the LUA interface "job.passes".
In the first pass, you store your value. For example:
local passdata = job.passes.define("mystuff") --I usually define this at
the top of my script and reuse it.
passdata["somevalue"] = "hello world";
Then in the subsequent runs you can access
local lastpassdata = job.passes.getcollected("mystuff") --Same here...
print(lastpassdata["somevalue"])
Best regards,
Andreas
___________________________________________________________________________________
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:[~2016-03-17 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 20:04 Romain Diss
2016-03-15 21:55 ` Hans Hagen
2016-03-16 21:47 ` Romain Diss
2016-03-17 8:11 ` Andreas Schneider [this message]
2016-03-17 12: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=42a53307693b3de32917ff53aef43cff@chemnitz.dyndns.aksdb.de \
--to=aksdb@gmx.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).