public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Peter Tirrell <ptirrell-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Can pandoc convert using UNC paths on Windows?
Date: Wed, 07 Nov 2018 15:07:55 -0800	[thread overview]
Message-ID: <yh480k8t24cwqc.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <f5356d68-e4be-413e-b862-900f5302dab9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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.


  parent reply	other threads:[~2018-11-07 23: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 [this message]
2018-11-08  9:07   ` Philip Hodder

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=yh480k8t24cwqc.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=ptirrell-Re5JQEeQqe8AvxtiuMwx3w@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).