From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Anton Shepelev
<anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc unable to access remote shares on Windows?
Date: Tue, 11 Aug 2020 12:28:06 -0700 [thread overview]
Message-ID: <m2364thtix.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <20200811181415.89ccef3a90a15783ceb1c261-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Possibly relevant issue
https://github.com/jgm/pandoc/issues/5127
Try with forward slashes!
Anton Shepelev <anton.txt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hello, all
>
> Being loth to store non-source files in version con-
> trol, I have decided to keep my reference document
> in a Windows share. But Pandoc seems unable to ac-
> cess the remote path. When I invoke it with
>
> --reference-doc=\\SRV3\\BinRes\Pandoc\style.docx
>
> it terminates with the error:
>
> pandoc: \\SRV3\\BinRes\Pandoc\style.docx:
> openBinaryFile: does not exist (No such file or directory)
>
> So I am forced to copy the style.docx locally in the
> build batch file:
>
> copy \\SRV3\\BinRes\Pandoc\style.docx .
>
> pandoc -f markdown -t docx ^
> --reference-doc=style.docx -N ^
> intdb.md -o intdb.docx
>
> del style.docx
>
> It works, but copying all remote resources locally
> just to make them accessible to Pandoc is ugly. Is
> there a better solution? Why is it that `copy' can
> access the remote path and Pandoc cannot?
>
> --
> Please, do not forward replies to the list to my e-mail.
>
> --
> 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/20200811181415.89ccef3a90a15783ceb1c261%40gmail.com.
next prev parent reply other threads:[~2020-08-11 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 15:14 Anton Shepelev
[not found] ` <20200811181415.89ccef3a90a15783ceb1c261-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-11 19:28 ` John MacFarlane [this message]
2020-08-11 21:15 ` Anton Shepelev
[not found] ` <20200812001505.bb45f82028c02553a07dec0a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-11 23:09 ` 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=m2364thtix.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=anton.txt-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).