From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Victor Hupay
<impoorbuthappy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: error producing PDF (@shorttitle)
Date: Sun, 16 Sep 2018 20:56:36 -0700 [thread overview]
Message-ID: <m2pnxckc97.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <9f44c97f-ae0f-4d73-a9fe-58a74f029c35-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
It seems to be caused by the `man` class option. (Not
sure what that does, but if you take it out you don't
get the error.)
Beyond that I'm not sure. But if you use pandoc to
create a minimal tex file with which you can reproduce
the error, you may be able to get help on a TeX forum.
(By minimal, I mean: strip out everything you can
take out and still get the same error.)
prev parent reply other threads:[~2018-09-17 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 3:44 Victor Hupay
[not found] ` <9f44c97f-ae0f-4d73-a9fe-58a74f029c35-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-09-17 3:56 ` John MacFarlane [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=m2pnxckc97.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=impoorbuthappy-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).