ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "kauśika cittūr via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: "kauśika cittūr" <citturs@gmail.com>
Subject: Cannot access Lua function
Date: Sat, 30 Oct 2021 11:55:37 +0530	[thread overview]
Message-ID: <5770315.lOV4Wx5bFT@sreeramtplt> (raw)

Dear list,

In one of my documents I have this lua block –
\startluacode
local metadata = lpdf.getmetadata();
⋮
\stopluacode
to modify some metadata fields.

The file compiles with the latest LMTX (2021.10.28) without any errors but no 
PDF is produced. In the log, the following line is present :

backend         > blocked > function 'getmetadata' is not accessible

I recall that this was working just fine some days back.

Please advise.

Thanks,
kauśika


___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2021-10-30  6:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30  6:25 kauśika cittūr via ntg-context [this message]
2021-10-30 11:27 ` Hans Hagen via ntg-context
2021-10-30 12:29   ` kauśika cittūr via ntg-context
2021-10-30 15:46     ` Hans Hagen via ntg-context
2021-10-31  4:35       ` kauśika cittūr via ntg-context
2021-10-31  9:13         ` Hans Hagen via ntg-context
2021-10-31 16:15           ` kauśika cittūr via ntg-context
2021-11-02  5:18           ` Aditya Mahajan via ntg-context

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=5770315.lOV4Wx5bFT@sreeramtplt \
    --to=ntg-context@ntg.nl \
    --cc=citturs@gmail.com \
    /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).