From: Michael Becker <michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Getting started with YAML
Date: Tue, 14 Sep 2021 08:54:27 -0700 (PDT) [thread overview]
Message-ID: <13939c88-9e2b-4b6e-b51b-ac9f93d271cfn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]
Hi all, I apologies for the newbie question, but I really don't understand
how to connect a YAML document to my pandoc processing? I have the doc.
Where do I put it? In the header of the file? in a data directory? If a
data directory, how do I give it a path. Can I combine both a bibliography
and a yaml document, or should I be using a metadata document?
I've read the documentation, but it is not making sense to me. If someone
can point me down the right path, I'd appreciate it.
--
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/13939c88-9e2b-4b6e-b51b-ac9f93d271cfn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1217 bytes --]
next reply other threads:[~2021-09-14 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 15:54 Michael Becker [this message]
[not found] ` <13939c88-9e2b-4b6e-b51b-ac9f93d271cfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-14 18:11 ` Jeremy Theler
[not found] ` <284636d2a3c622f2c8af5ca3314e3630b12065f4.camel-24em0bpozeFWk0Htik3J/w@public.gmane.org>
2021-09-14 18:21 ` Michael Becker
2021-09-15 8:03 ` BPJ
[not found] ` <CADAJKhBWP9y=Ah_BAR5061nuhFKR5s7GZXMovn1h+sLx3cP0Ww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-09-16 21:17 ` Michael Becker
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=13939c88-9e2b-4b6e-b51b-ac9f93d271cfn@googlegroups.com \
--to=michael-qf1xymwe1uwv0rdu9s6tydbpr1lh4cv8@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).