From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: LaTeX siunitx macros not working
Date: Sun, 21 May 2017 23:50:48 -0700 (PDT) [thread overview]
Message-ID: <a4a4e3f0-c549-4a1f-90a5-d21d7143d9cd@googlegroups.com> (raw)
In-Reply-To: <0de9dc67-40f0-4938-90ee-51ca2f7e2818-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 166 bytes --]
If you are compiling from dev (master branch) and expect it to work, you should be disappointed.
They are for developers, do so only if you want to help developing.
prev parent reply other threads:[~2017-05-22 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 3:15 Kurt Blarrel
[not found] ` <0de9dc67-40f0-4938-90ee-51ca2f7e2818-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-05-20 7:25 ` Andrew Dunning
2017-05-22 6:50 ` Kolen Cheung [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=a4a4e3f0-c549-4a1f-90a5-d21d7143d9cd@googlegroups.com \
--to=christian.kolen-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).