From: "Procházka Lukáš Ing." <LPr@pontex.cz>
To: ConTeXt <ntg-context@ntg.nl>
Subject: 'figures.getinfo()' not to exit ConTeXt
Date: Thu, 06 Dec 2018 11:20:44 +0100 [thread overview]
Message-ID: <op.ztli0usq62epfj@lpr> (raw)
Hello,
I'm using the following code, mentioned here some time ago, to get some info about PDF:
----
\startluacode
figures.getinfo = function(name, page)
if type(name) == "string" then
name = { name = name, page = page }
end
if name.name then
local data = figures.push(name)
--figures.identify()
local ok, res = pcall(figures.identify)
print(">>1", ok, res)
--figures.check()
local ok, res = pcall(figures.check)
print(">>2", ok, res)
figures.pop()
return data
end
end
local data = figures.getinfo("NonExisting.pdf")
\stopluacode
----
The problem is that once the PDF file doesn't exist, the function causes ConTeXt to exit, even when I enclose 'figure.check()' into the 'pcall' (to be handled like try/catch mechanism).
Is there a way so that the function 'figures.getinfo()' does't exit ConTeXt, it just returns 'nil', or even gives info which directories (or even which file types) were searched?
TIA.
Best regards,
Lukas
--
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS: nrpt3sn | IČO: 40763439
Bezová 1658
147 14 Praha 4
Mob.: +420 702 033 396
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2018-12-06 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 10:20 Procházka Lukáš Ing. [this message]
2018-12-06 10:23 ` luigi scarso
2018-12-06 10:57 ` Procházka Lukáš Ing.
2018-12-06 10:57 ` luigi scarso
2018-12-06 11:05 ` Hans van der Meer
2018-12-06 11:25 ` Wolfgang Schuster
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=op.ztli0usq62epfj@lpr \
--to=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).