From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Converting to pdf: `pandoc: openFile: resource busy (file is locked)`
Date: Fri, 10 Mar 2023 10:12:33 -0800 [thread overview]
Message-ID: <1364E4F3-B8B9-4B8F-9D99-90634594C09C@gmail.com> (raw)
In-Reply-To: <6076f667-a748-4e17-969c-9264882cd273n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Works ok for me on Monterey. I don't have a Ventura machine to test on.
Can anyone else who is running Ventura try to reproduce this?
Also, do you have the same problem producing a pdf with --pdf-engine=pdflatex ?
> On Mar 9, 2023, at 12:24 PM, Elephant <rohit.jagan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hello,
>
> When I try to to convert form markdown to pdf with weasyprint or wkhtmltopdf, I get the error message `pandoc: openFile: resource busy (file is locked)`.
>
> For example,
>
> > echo "example" | pandoc -o example.pdf --pdf-engine=wkhtmltopdf
> [WARNING] This document format requires a nonempty <title> element.
> Defaulting to '-' as the title.
> To specify a title, use 'title' in metadata or --metadata title="...".
> pandoc: openFile: resource busy (file is locked)
>
> and
>
> > echo "example" | pandoc -o example.pdf --pdf-engine=weasyprint
> [WARNING] This document format requires a nonempty <title> element.
> Defaulting to '-' as the title.
> To specify a title, use 'title' in metadata or --metadata title="...".
> pandoc: openFile: resource busy (file is locked)
>
> I'm on macos Ventura 13.2.1 and pandoc 3.1. Any idea how to fix this?
>
> --
> 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/6076f667-a748-4e17-969c-9264882cd273n%40googlegroups.com.
prev parent reply other threads:[~2023-03-10 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 20:24 Elephant
[not found] ` <6076f667-a748-4e17-969c-9264882cd273n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-10 3:24 ` A A
[not found] ` <CAMwawgMyFr+ULLO7gAG_ScOZRutfosxdDih7m3SyDbpx08FW7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-10 4:25 ` Elephant
[not found] ` <ea4428ac-8ce0-4b96-8830-6d8c2356bd49n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-10 12:41 ` 'William Lupton' via pandoc-discuss
[not found] ` <CAEe_xxgAtJ-pZ0c9BsHsusA1uCzPuebD3tg37yL+uN4SccLGhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-10 19:33 ` Elephant
2023-03-10 18:12 ` John MacFarlane [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=1364E4F3-B8B9-4B8F-9D99-90634594C09C@gmail.com \
--to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@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).