From: zmwknPUyWz <zmwknpuywz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: unrecognized option: resource path
Date: Tue, 29 Oct 2019 00:33:42 -0700 (PDT) [thread overview]
Message-ID: <34e50490-f40f-4777-8275-e82850a33c43@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]
Hi everyone,
I am trying to convert a markdown file into a docx file. For this, I would
like to specify an additional folder containing the images. When using the
option --resource-path, I am receiving the following error:
pandoc: unrecognized option `--resource-path=./pandoc'
I already tried different versions of the path, such as absolute or
relative path, with quotes,...
The command I have been using is the following:
pandoc --resource-path=./pandoc -f markdown -t docx -o document.docx
document.md
I am using pandoc 1.19.2.4 on Ubuntu 18.04.
Am I missing something? Do you have any idea what I could try to resolve
the issue?
I appreciate any help. And I'm happy to provide any info if I've forgotten
something.
--
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/34e50490-f40f-4777-8275-e82850a33c43%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3876 bytes --]
next reply other threads:[~2019-10-29 7:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 7:33 zmwknPUyWz [this message]
[not found] ` <34e50490-f40f-4777-8275-e82850a33c43-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-29 23:21 ` John MacFarlane
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=34e50490-f40f-4777-8275-e82850a33c43@googlegroups.com \
--to=zmwknpuywz-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).