public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Hans Kunkell <hanzukun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Full path to reference doc does not work in Cygwin
Date: Tue, 18 Jun 2019 12:13:40 +0900	[thread overview]
Message-ID: <CAMx_B2a2pxv9Bx58hF9v4U81oZKatDRGjsLwP+PE9-gvE3PwPA@mail.gmail.com> (raw)

Hi!

This is my first message, so I would like to thank all contributors
for this great software!

I have an issue with full path names to --reference-doc and --data-dir.

I run pandoc from within a bash script running in Cygwin under Windows
7. If I use full path information to the --reference-doc or
--data-dir, I get the error
openBinaryFile: does not exist (No such file or directory)

For example, these 2 examples does not work:
pandoc --reference-doc=/home/hans/Documents/script/reference.odt -o
test.odt input.md
pandoc --reference-doc=/cygdrive/c/Users/Hans/Documents/script/reference.odt
-o test.odt input.md

For the case of --data-dir I will not get an error but it is obvious
that my reference.odt has not been applied to the output file.


These works in Cygwin environment:
pandoc --reference-doc=../script/reference.odt -o test.odt input.md
                              # relative path
pandoc --reference-doc='C:\Users\Hans\Documents\script\reference.odt'
-o test.odt input.md           # windows style full path
pandoc --data-dir='C:\Users\Hans\Documents\script\' -o test.odt
input.md                             # windows style full path

I have tested both Pandoc 2.7.2 and 2.7.3 with same result.
Cygwin version: CYGWIN_NT-6.1 dator 3.0.1(0.338/5/3) 2019-02-20 10:19
x86_64 Cygwin

Full paths works in CMD.exe and in Linux (Ubuntu with pandoc 2.7.2).
For me it is of a smaller issue, but
pandoc -s --reference-doc=~/Documents/script/reference.odt -o test.odt
input.md                      # Does not work with ~ (tilde)
will also not work.

Has anyone else experienced these issues?
I can workaround this but I think it would be good if it worked.

Regards
Hans


             reply	other threads:[~2019-06-18  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  3:13 Hans Kunkell [this message]
     [not found] ` <CAMx_B2a2pxv9Bx58hF9v4U81oZKatDRGjsLwP+PE9-gvE3PwPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-07-11 21:34   ` John MacFarlane
     [not found]     ` <m2muhk6ysl.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-07-12  4:54       ` Hans Kunkell

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=CAMx_B2a2pxv9Bx58hF9v4U81oZKatDRGjsLwP+PE9-gvE3PwPA@mail.gmail.com \
    --to=hanzukun-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).