From: Marc Chantreux <eiro-fbXiWI9j2LLYtjvyW6yDsg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Absolute path in for loop / output?
Date: Tue, 7 Sep 2021 21:26:15 +0200 [thread overview]
Message-ID: <YTe8189Jim/Iqif5@prometheus.u-strasbg.fr> (raw)
In-Reply-To: <78489a20-5148-4826-ab6a-b43fa48938d4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
hello,
> for f in "/users/myname/desktop/test/input/"*.md; \
> do \
> pandoc "$f" \
> --standalone \
> -o "/users/myname/desktop/test/output/"${f%.md}.htm; \
> done
close :) this should do the trick:
base=/users/myname/desktop/test
pushd $base/input
for f in *.md ; do
pandoc "$f" -s -o $base/output/${f.md}.htm
done
popd
if you use zsh and don't care about a subshell, i would have writen
( base=/users/myname/desktop/test
cd $base/input
for f (*.md) pandoc "$f" -s -o $base/output/$f:r.htm )
however i would like to mention make as a better solution:
* a makefile to do the same job will be
BASE = /users/myname/desktop/test
SRCS != ls ${BASE}/input/*.md
PAGES = ${SRCS:${BASE}/input/%.md=${BASE}/output/%.htm}
all : ${PAGES}
${BASE}/output/%.htm: ${BASE}/input/%.md
pandoc -s -o $@ $<
clean:; rm -rf ${BASE}/o/*
* you can just type
make # build the missing pages one by one
make -j4 # build the missing pages four by four
make -b # rebuild every pages
make clean # remove all the pages
regards
marc
next prev parent reply other threads:[~2021-09-07 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 15:21 Martin Post
[not found] ` <78489a20-5148-4826-ab6a-b43fa48938d4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-07 15:49 ` Bastien DUMONT
2021-09-07 17:06 ` John MacFarlane
2021-09-07 19:26 ` Marc Chantreux [this message]
[not found] ` <YTe8189Jim/Iqif5-AWr1gsF+PRs9Vg2ZJzWmxBLO4URiXwcH@public.gmane.org>
2021-09-11 19:52 ` Martin Post
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=YTe8189Jim/Iqif5@prometheus.u-strasbg.fr \
--to=eiro-fbxiwi9j2llytjvyw6ydsg@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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).