From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Steve Pederson
<stephen.pederson.au-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: openBinaryFile: does not exist
Date: Thu, 24 Sep 2020 09:05:26 -0700 [thread overview]
Message-ID: <m2blhvcg8p.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <m2a6xicqjn.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
Nightlies are now working again, so please test with a nightly build.
https://github.com/jgm/pandoc/actions/runs/270103289
John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
> Was going to say: Why don't you try a nightly and see if the recent change
> fixes things? That would be good to know.
>
> But I just noticed that the nightlies have been broken for a few
> days. Will look into this.
>
> Steve Pederson <stephen.pederson.au-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
>> Hi,
>>
>> I'm trying to help a colleague running on Windows with a networked drive at
>> a tertiary institution (that file path is horrific...). The installation of
>> 2.10.1 appears to have gone well and running the first few examples
>> from https://pandoc.org/getting-started.html also work, UNTIL we parse from
>> the file test1.md, created using Notepad as instructed.
>>
>> pandoc test1.md -f markdown -t html test1.html
>> pandoc: test1.html: openBinaryFile: does not exist (No such file or
>> directory)
>>
>> We actually went back to pandoc directly as a stand-alone tool because no
>> RMarkdown files are compiling inside RStudio, and they thought is was an R
>> issue. The same error was appearing there.
>>
>> I notice that this behaviour (https://github.com/jgm/pandoc/issues/5127)
>> was marked resolved in commit 26ed7fb4f9e95a only a couple of days ago. Is
>> there a fix that will appear in a release soon as it' doesn't appear to be
>> in 2.10.1?
>>
>> Thanks in advance,
>>
>> Steve
>>
>>
>> --
>> 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/bc5942a7-0bc0-4a84-b377-15a4c9a50cd5n%40googlegroups.com.
next prev parent reply other threads:[~2020-09-24 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 5:00 Steve Pederson
[not found] ` <bc5942a7-0bc0-4a84-b377-15a4c9a50cd5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-22 5:46 ` John MacFarlane
[not found] ` <m2a6xicqjn.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-24 16:05 ` John MacFarlane [this message]
[not found] ` <m2blhvcg8p.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-24 16:36 ` Steve Pederson
2020-10-20 4:28 ` Steve Pederson
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=m2blhvcg8p.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=stephen.pederson.au-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).