From: Philipp Gesang <gesang@stud.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [.tuc] oddity when storing a table
Date: Mon, 17 Sep 2012 23:13:49 +0200 [thread overview]
Message-ID: <20120917211349.GB7316@phlegethon> (raw)
In-Reply-To: <505641AC.9040404@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2583 bytes --]
···<date: 2012-09-16, Sunday>···<from: Hans Hagen>···
> On 16-9-2012 19:17, Philipp Gesang wrote:
> >Bug?
>
> no, feature. job variables are just key/values and accessible at the
> tex end (you store 'works too' in 'bar')
Ok, I wasn’t aware of this restriction.
> if you want arbitrary data to be stores you need to used datasets,
> as explained in
>
> http://wiki.contextgarden.net/Command/definedataset
Hmm, the wiki only covers the TeX macro interface whilst I am
mainly concerned with passing stuff right from the Lua end.
From my reading of core-dat.lua I gather that there is not really
a way to dump any Lua table (array or hash or mixed) via
datasets. Except directly writing to “tobesaved”.
·······································································
\starttext
\startluacode
local n, t, d = job.datasets.setdata{
name = "not enough!!!11!1! grr!",
delay = interfaces.variables.no,
data = "a=b,c=d,1=foo,2=bar,nested={second={third=whatever}}",
}
job.datasets.tobesaved.works_for_me = {
this = { does = { "work", "for", nested = { "tables", "!", {{}} } } }
}
table.print(job.datasets.getdata("works_for_me", "this"), "this")
\stopluacode
\stoptext
·······································································
I hesitate to wikify the latter, though.
Philipp
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
> | 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2012-09-17 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 17:17 Philipp Gesang
2012-09-16 21:16 ` Hans Hagen
2012-09-17 21:13 ` Philipp Gesang [this message]
2012-09-17 22:19 ` 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=20120917211349.GB7316@phlegethon \
--to=gesang@stud.uni-heidelberg.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).