From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: `-t markdown` refuses to render citations
Date: Mon, 16 Sep 2019 07:57:24 -0400 [thread overview]
Message-ID: <716f7d1c-e8a5-5982-2a77-2455ac4eae51@reagle.org> (raw)
In-Reply-To: <yh480kh85f6b9a.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
On 9/13/19 7:13 PM, John MacFarlane wrote:
> -t markdown-citations
>
> With the default +citations, the markdown citation syntax
> is enabled, so you'll get @item1. With -citations, you'll
> get the rendered citation.
Thank you.
prev parent reply other threads:[~2019-09-16 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 20:57 Joseph Reagle
[not found] ` <25f74181-be38-d970-46f0-d1c940dcee2c-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-13 23:13 ` John MacFarlane
[not found] ` <yh480kh85f6b9a.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-16 11:57 ` Joseph Reagle [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=716f7d1c-e8a5-5982-2a77-2455ac4eae51@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).