From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Any ConTeXt-Lua changes
Date: Mon, 14 Jan 2013 15:21:15 +0100 [thread overview]
Message-ID: <C30F2902-5FB3-41C6-A12B-53C4ACDDE93C@gmail.com> (raw)
In-Reply-To: <1E5A50C784A8AD44B420EF5A1E9B2806C81FEF00@e14mbx20n.Enterprise.emory.net>
Am 14.01.2013 um 15:08 schrieb "Rogers, Michael K" <mroge02@emory.edu>:
> Hi,
>
> I wrote Lua routines a while back that parse a string representation of a weekly schedule to create a table representation of the schedule. It worked last fall. Certainly in August, 2012 and I think at least as late October. I just tried it again, but it failed; and it failed on the same file it worked on before.
>
> Before I roll up my sleeves and starting digging through the code, I was wondering if something had changed in the last two or three months that I should know about. No MWE for you, but here's the ConTeXt command that sends an ID (#1) and a parameters (#2) to Lua
>
> \def\defineschedule{\dodoubleempty\dodefineschedule}
> \def\dodefineschedule[#1][#2]{\ctxlua{userdata.schedule.new("#1","#2")}}
What’s the error message, there is no way to tell what’s wrong with only these two code lines.
Wolfgang
___________________________________________________________________________________
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:[~2013-01-14 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 14:08 Rogers, Michael K
2013-01-14 14:21 ` Wolfgang Schuster [this message]
2013-01-14 14:48 ` Rogers, Michael K
2013-01-14 15:10 ` Peter Münster
2013-01-14 17:33 ` 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=C30F2902-5FB3-41C6-A12B-53C4ACDDE93C@gmail.com \
--to=wolfgang.schuster@gmail.com \
--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).