From: Martin Post <martinpostberlin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Shell (zsh) for loop: apply correct suffix based on Pandoc output format?
Date: Mon, 2 Oct 2023 06:58:57 -0700 (PDT) [thread overview]
Message-ID: <e8d686ec-e667-4dff-97c3-133af2a6f731n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1046 bytes --]
I used to do this (in macOS / zsh), as seen in the Pandoc FAQ:
for f in *.md;
do pandoc \
--defaults=defaults.yml \
"$f" \
--output="${f%.md}.htm";
done
But I am now changing output formats in defaults.yml (or additional default
files), e.g. “to: docx”, and the target files obviously shouldn’t have
“.htm” then.
How can I modify the for loop so the correct suffix is applied for the
output format set in a defaults file?
(I realize I could manually add a “output-format-suffix” shell variable and
use that in the loop, but I hope there’s something more elegant than that.)
Thank you.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e8d686ec-e667-4dff-97c3-133af2a6f731n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1383 bytes --]
next reply other threads:[~2023-10-02 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 13:58 Martin Post [this message]
[not found] ` <e8d686ec-e667-4dff-97c3-133af2a6f731n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-02 14:17 ` Bastien DUMONT
2023-10-02 15:06 ` Martin Post
[not found] ` <5843b3a9-e780-4816-8a6d-70277d1295d6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-02 15:18 ` Bastien DUMONT
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=e8d686ec-e667-4dff-97c3-133af2a6f731n@googlegroups.com \
--to=martinpostberlin-re5jqeeqqe8avxtiumwx3w@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).