From: Oliver Baumann <news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Embed command line options in the Markdown source
Date: Wed, 12 Apr 2023 04:41:40 -0700 (PDT) [thread overview]
Message-ID: <844066b9-163f-4890-b981-74545070ee6dn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 750 bytes --]
I use pandoc to generate LaTeX PDFs from Markdown sources.
Often I have quite long command lines with
pandoc myarticle.md --standalone --include-in-header ...
Now I would like to provide these options in the YAML of theMarkdown
source. In the past I used panzer for this, but is this now
with pandoc 3 maybe built into pandoc itself?
--
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/844066b9-163f-4890-b981-74545070ee6dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3425 bytes --]
next reply other threads:[~2023-04-12 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 11:41 Oliver Baumann [this message]
[not found] ` <844066b9-163f-4890-b981-74545070ee6dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-12 12:48 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <a6f97768d4e3419780f4df6456356cf0-NSENcxR/0n0@public.gmane.org>
2023-04-14 0:56 ` news-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA
[not found] ` <CBF27702-32AA-4A20-B546-15B0A8C5B05D-WPTjrydoUPgeaOpM6FAJmQkbCANdLtlA@public.gmane.org>
2023-04-14 5:31 ` AW: " denis.maier-NSENcxR/0n0
[not found] ` <ec59d4a1f494447c987ef64d1c957617-NSENcxR/0n0@public.gmane.org>
2023-04-14 15:10 ` 'Marek Stepanek' via pandoc-discuss
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=844066b9-163f-4890-b981-74545070ee6dn@googlegroups.com \
--to=news-wptjrydoupgeaopm6fajmqkbcandltla@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).