From: Philip Hodder <phil-jvooPmwWovGx7wk7FZxnQA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Can pandoc convert using UNC paths on Windows?
Date: Thu, 8 Nov 2018 01:07:08 -0800 (PST) [thread overview]
Message-ID: <758175cf-cf3e-4b80-ab21-68594fd9a644@googlegroups.com> (raw)
In-Reply-To: <f5356d68-e4be-413e-b862-900f5302dab9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1540 bytes --]
I don't know how Haskell processes file paths but have you tried escaping
the slashes? E.g.
pandoc "\\\\network\path\to\file.md"
or even using Unix like path separators:
pandoc "\\\\network/path/to/file.md"
Phil
On Wednesday, November 7, 2018 at 9:34:53 PM UTC, Peter Tirrell wrote:
>
> I'm trying to run pandoc, on Windows, against a file on a network share.
> I'm calling the executable within a Powershell prompt, but the same
> behavior happens in CMD. I have tried calling
>
> pandoc "\\network\path\to\file.md"
>
> and changing to the UNC folder in Powershell and calling
>
> pandoc .\file.md
>
> and get the same error message: "openBinaryFile: does not exist (no such
> file or directory".
>
> My hunch is that pandoc doesn't support UNC paths, but I haven't been able
> to find a quick explicit answer as to whether this should work or not. If
> it isn't supported I'll give up and move on, but if it is - what might I be
> doing wrong?
>
--
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/758175cf-cf3e-4b80-ab21-68594fd9a644%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2375 bytes --]
prev parent reply other threads:[~2018-11-08 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 21:34 Peter Tirrell
[not found] ` <f5356d68-e4be-413e-b862-900f5302dab9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-11-07 23:07 ` John MacFarlane
2018-11-08 9:07 ` Philip Hodder [this message]
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=758175cf-cf3e-4b80-ab21-68594fd9a644@googlegroups.com \
--to=phil-jvoopmwwovgx7wk7fzxnqa@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).