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.