* Can pandoc convert using UNC paths on Windows?
@ 2018-11-07 21:34 Peter Tirrell
[not found] ` <f5356d68-e4be-413e-b862-900f5302dab9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Peter Tirrell @ 2018-11-07 21:34 UTC (permalink / raw)
To: pandoc-discuss
[-- Attachment #1.1: Type: text/plain, Size: 1218 bytes --]
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/f5356d68-e4be-413e-b862-900f5302dab9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1812 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Can pandoc convert using UNC paths on Windows?
[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
1 sibling, 0 replies; 3+ messages in thread
From: John MacFarlane @ 2018-11-07 23:07 UTC (permalink / raw)
To: Peter Tirrell, pandoc-discuss
I'm afraid I don't know, and I don't have a Windows
setup to test on. Maybe someone else here can help.
I would have thought that at least the second version
should have worked.
Peter Tirrell <ptirrell-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> 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/f5356d68-e4be-413e-b862-900f5302dab9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Can pandoc convert using UNC paths on Windows?
[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
1 sibling, 0 replies; 3+ messages in thread
From: Philip Hodder @ 2018-11-08 9:07 UTC (permalink / raw)
To: pandoc-discuss
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-11-08 9:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-11-07 21:34 Can pandoc convert using UNC paths on Windows? 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 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).