From: "Pedro P. Palazzo" <pedro.palazzo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Citeproc error: openBinaryFile does not exist
Date: Wed, 11 Nov 2020 15:00:28 -0800 (PST) [thread overview]
Message-ID: <239fea53-40c1-4ed2-bc70-cdaf088a8770n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 987 bytes --]
I just installed Pandoc 2.11.1.1 and Citeproc 0.1.1.1 through `cabal
new-install -f executable` on a MacOS 10.13 (High Sierra); my cabal is at
version 3.2.0.0. The installation of citeproc showed a few `The import of
‘Data.Semigroup’ is redundant` warnings, no errors.
When I try to use the --filter citeproc on any file, I get the error
`citeproc: html: openBinaryFile: does not exist (No such file or
directory)` --- where `html` can be replaced by any file format I'm trying
to convert to.
Any thoughts? No pandoc.out file is being generated.
--
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/239fea53-40c1-4ed2-bc70-cdaf088a8770n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1312 bytes --]
next reply other threads:[~2020-11-11 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 23:00 Pedro P. Palazzo [this message]
[not found] ` <239fea53-40c1-4ed2-bc70-cdaf088a8770n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-11 23:02 ` Pedro P. Palazzo
2020-11-11 23:25 ` John MacFarlane
[not found] ` <m2v9ebh3xa.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-12 0:16 ` Pedro P. Palazzo
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=239fea53-40c1-4ed2-bc70-cdaf088a8770n@googlegroups.com \
--to=pedro.palazzo-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).