From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Iterate through a directory
Date: Mon, 4 Jul 2016 18:30:55 +0200 [thread overview]
Message-ID: <189e2309-5429-0754-f0f9-5e31f4877dad@wxs.nl> (raw)
In-Reply-To: <24117c14-e8b0-3bbf-6122-342303400e0c@gmail.com>
On 7/4/2016 5:52 PM, Keith McKay wrote:
> Colleagues
>
> I'm preparing a booklet of figures which are stored in a directory,
> however their is no structure in their naming. I could go through them
> all and rename them along the lines of Pict1.jpg, Pict2.jpg etc and
> \dostepwiserecurse as in the example below
>
>
> \setupexternalfigures [directory={/a/directory}]
> \starttext
> \dostepwiserecurse{1}{10}{1}
> {
> \externalfigure[Pict\recurselevel.jpg]
> }
> \stoptext
>
> However, I was wondering if was possible to iterate through the
> directory using a wildcard and have something like
>
> \externalfigure[*.jpg}
>
> to make it generic, or would I have to use lua.
\startluacode
for _, name in ipairs(dir.glob("*.jpg")) do
context.externalfigure { name }
end
\stopluacode
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-07-04 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 15:52 Keith McKay
2016-07-04 16:30 ` Hans Hagen [this message]
2016-07-04 18:26 ` Keith McKay
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=189e2309-5429-0754-f0f9-5e31f4877dad@wxs.nl \
--to=pragma@wxs.nl \
--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).