From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: check installed program using Lua
Date: Tue, 2 Nov 2021 20:01:07 +0100 [thread overview]
Message-ID: <2c6d0b3a-035b-c1b2-ea7c-cb7a1c28dd4e@gmx.es> (raw)
In-Reply-To: <5ce3bc9f-7cc3-9731-8e49-331654de352e@xs4all.nl>
On 11/1/21 5:13 PM, Hans Hagen via ntg-context wrote:
> On 11/1/2021 2:26 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> Is there a way to wrap os.exec() in the sample so that it only runs if
>> "dir" is available?
>>
>> I know that os.name would be an option here, but not in my real world
>> document.
>
> \starttext
> \startluacode
> if lfs.isfile(tex.jobname .. ".pdf") then
> context("YES")
> end
> if lfs.isfile(file.addsuffix(environment.outputfilename,"pdf")) then
> context("YES")
> end
> if #dir.glob(file.addsuffix(environment.outputfilename,"pdf")) > 0 then
> context("YES")
> end
> \stopluacode
> \stoptext
Many thanks for your reply, Hans.
I can see that I explained my question poorly, but your code fits me in
other case.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-11-02 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 13:26 Pablo Rodriguez via ntg-context
2021-11-01 14:10 ` Taco Hoekwater via ntg-context
2021-11-02 18:59 ` Pablo Rodriguez via ntg-context
2021-11-01 16:13 ` Hans Hagen via ntg-context
2021-11-02 19:01 ` Pablo Rodriguez via ntg-context [this message]
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=2c6d0b3a-035b-c1b2-ea7c-cb7a1c28dd4e@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).