From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Hans Kunkell <hanzukun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Full path to reference doc does not work in Cygwin
Date: Thu, 11 Jul 2019 14:34:18 -0700 [thread overview]
Message-ID: <m2muhk6ysl.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <CAMx_B2a2pxv9Bx58hF9v4U81oZKatDRGjsLwP+PE9-gvE3PwPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Cygwin is tough. Certain things about pandoc's
file path handling depend on the platform pandoc
is compiled on. So a pandoc compiled on windows
may have expectations that are not met in Cygwin.
See https://github.com/jgm/pandoc/issues/5451
which may be somehow related.
You can put up an issue on this if you like.
About the other issue:
> 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.
This is because ~ is interpreted by the shell, normally, but
in this context it is just passed on literally to pandoc.
If you try with a space in place of = it should work.
next prev parent reply other threads:[~2019-07-11 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 3:13 Hans Kunkell
[not found] ` <CAMx_B2a2pxv9Bx58hF9v4U81oZKatDRGjsLwP+PE9-gvE3PwPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-07-11 21:34 ` John MacFarlane [this message]
[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=m2muhk6ysl.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=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).