From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Shell (zsh) for loop: apply correct suffix based on Pandoc output format?
Date: Mon, 2 Oct 2023 15:18:38 +0000 [thread overview]
Message-ID: <ZRrfTpqIopvrxPei@localhost> (raw)
In-Reply-To: <5843b3a9-e780-4816-8a6d-70277d1295d6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
That's why I wrote the last sentence!
Le Monday 02 October 2023 à 08:06:48AM, Martin Post a écrit :
> Thank you, Bastien. This is a good idea, but the Pandoc output format is not
> necessarily the proper generic file suffix. E.g., for to: markdown or
> markdown_strict, one would want/expect “.md”, html5 = .html etc. For
> chunkedhtml, it would actually (have to) be empty, so Pandoc will create a
> folder with HTML files.
>
> Hmm.
>
> Bastien DUMONT schrieb am Montag, 2. Oktober 2023 um 16:17:28 UTC+2:
>
> I would search for the output suffix in the YAML file itself:
>
> export SUFFIX="$(grep -x 'to: .*' defaults.yml | cut -d ' ' -f 2)";
> for f in *.md;
> do pandoc \
> --defaults=defaults.yml \
> "$f" \
> --output="${f%.md}.$SUFFIX";
> done
>
> Instead of "to", you can use a dedicated variable in the YAML file if you
> export to output formats whose name differ from their file suffix (e.g.
> latex/tex or commonmark/md).
>
> Le Monday 02 October 2023 à 06:58:57AM, Martin Post a écrit :
> > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [2][1]https://groups.google.com/
> d/msgid/
> > pandoc-discuss/e8d686ec-e667-4dff-97c3-133af2a6f731n%[2]
> 40googlegroups.com.
> >
> > References:
> >
> > [1] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [2] [3]https://groups.google.com/d/msgid/pandoc-discuss/
> e8d686ec-e667-4dff-97c3-133af2a6f731n%40googlegroups.com?utm_medium=email&
> utm_source=footer
>
>
> --
> 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 [4]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [5]https://groups.google.com/d/msgid/
> pandoc-discuss/5843b3a9-e780-4816-8a6d-70277d1295d6n%40googlegroups.com.
>
> References:
>
> [1] https://groups.google.com/d/msgid/
> [2] http://40googlegroups.com/
> [3] https://groups.google.com/d/msgid/pandoc-discuss/e8d686ec-e667-4dff-97c3-133af2a6f731n%40googlegroups.com?utm_medium=email&utm_source=footer
> [4] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [5] https://groups.google.com/d/msgid/pandoc-discuss/5843b3a9-e780-4816-8a6d-70277d1295d6n%40googlegroups.com?utm_medium=email&utm_source=footer
--
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/ZRrfTpqIopvrxPei%40localhost.
prev parent reply other threads:[~2023-10-02 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 13:58 Martin Post
[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 [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=ZRrfTpqIopvrxPei@localhost \
--to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).