From: jcr <ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How do I write a standalone document with pandoc.write?
Date: Sun, 25 Sep 2022 03:25:54 -0700 (PDT) [thread overview]
Message-ID: <0a27b0df-a58b-4a4f-bb89-1a22e4ca6a07n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]
How do I tell `pandoc.write` to produce a standalone Markdown document
(with YAML metadata)? There's no `standalone` option for
`pandoc.WriterOptions`. I thought setting a template might work, but it
doesn't: the saved file does not contain a YAML block, even though the
document has metadata. My attempt is below:
```
function write_markdown_file(doc, filename)
local options = pandoc.WriterOptions{
template = pandoc.template.default('markdown')
}
local data = pandoc.write(doc, 'markdown', options)
local file <close>, error = io.open(filename, 'w')
if file == fail then
io.stderr:write(string.format('Failed to write Markdown file: %s\n',
error))
os.exit(1)
end
file:write(data)
end
```
I'm using pandoc 2.19.2.
--
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/0a27b0df-a58b-4a4f-bb89-1a22e4ca6a07n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1661 bytes --]
next reply other threads:[~2022-09-25 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 10:25 jcr [this message]
[not found] ` <0a27b0df-a58b-4a4f-bb89-1a22e4ca6a07n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-25 15:22 ` Albert Krewinkel
[not found] ` <878rm7scie.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-09-25 17:49 ` ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w
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=0a27b0df-a58b-4a4f-bb89-1a22e4ca6a07n@googlegroups.com \
--to=ffi.appdev-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).