* Full path to reference doc does not work in Cygwin
@ 2019-06-18 3:13 Hans Kunkell
[not found] ` <CAMx_B2a2pxv9Bx58hF9v4U81oZKatDRGjsLwP+PE9-gvE3PwPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Hans Kunkell @ 2019-06-18 3:13 UTC (permalink / raw)
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Full path to reference doc does not work in Cygwin
[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>
0 siblings, 1 reply; 3+ messages in thread
From: John MacFarlane @ 2019-07-11 21:34 UTC (permalink / raw)
To: Hans Kunkell, pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Full path to reference doc does not work in Cygwin
[not found] ` <m2muhk6ysl.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
@ 2019-07-12 4:54 ` Hans Kunkell
0 siblings, 0 replies; 3+ messages in thread
From: Hans Kunkell @ 2019-07-12 4:54 UTC (permalink / raw)
To: pandoc-discuss
[-- Attachment #1.1: Type: text/plain, Size: 1871 bytes --]
Dear John,
thank you for your reply!
I realized that I use Pandoc compiled for Windows and that is probably the
reason it behaves like this in Cygwin environment.
Changing = to space does not work either, and I assume it depends on the
differencies in environments.
I can workaround both of these problems (or use correct software in the
right environment).
Thank you!
Regards
Hans
Fredag 12 juli 2019 kl. 06:34:33 UTC+9 skrev John MacFarlane:
>
> 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.
>
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/51d284a3-a378-45d0-b0fd-569b13b4363b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3182 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-07-12 4:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-18 3:13 Full path to reference doc does not work in Cygwin Hans Kunkell
[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
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).