From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pdf-engine pdflatex not known
Date: Fri, 10 Nov 2017 21:58:01 -0500 [thread overview]
Message-ID: <20171111025801.GE16934@MacBook-Air-2.local> (raw)
In-Reply-To: <e9a5dc66-97b7-4842-bc39-71f9f2a83682-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
You only provided part of the log (and I didn't see any
error messages). Try converting with --pdf-engine=pdflatex
and a really simple input file like ("*hi*").
If it succeeds with the simple file, then the problem has
to do with the content in your file. In this case we'd
need to see more of the verbose log.
+++ Kyle Eggleton [Nov 10 17 18:48 ]:
> Hi John. Thanks for getting back. I have tried both - yes pdflatex is
> executable at /Libary/TeX/Root/bin/x86_64-darwin/pdflatex and at the
> new Tex-2017 installation at /Library/Tex/texbin. Yes I have tried
> putting pdf-engine=pdflatex in the command and this produces the error
> message "Error producing PDF" with no other details. The verbose log is
> attached above.
> On Saturday, November 11, 2017 at 3:38:49 PM UTC+13, John MacFarlane
> wrote:
>
> Have you verified that you have an executable file at
> /Library/TeX/Root/bin/x86_64-darwin/pdflatex ?
> If pdflatex is in your path, can you try just
> --pdf-engine=pdflatex ?
> +++ Kyle Eggleton [Nov 10 17 16:28 ]:
> > Hi, I have just updated to pandoc 2.0.1.1 on my Mac running
> MacOS
> > 10.12.6 and since updating I have been unable to generate PDFs.
> The
> > error message that I am getting is pdf-engine
> > /Library/Tex/Root/bin/x86-64-darwin/pdflatex not known.
> > My command is: pandoc -r markdown -markdown+smart -N --filter
> > /usr/local/bin/pandoc-crossref --filter
> /usr/local/bin/pandoc-citeproc
> > --pdf-engine=/Library/TeX/Root/bin/x86_64-darwin/pdflatex
> > --template=/Users/kyle/Documents/IT/Pandoc/templates/
> thesis.latex
> > [1]file.md -o file.pdf
> > This command was working fine prior to updating to the new
> version of
> > Pandoc (noting that the old command included
> > --latex-engine=path/to/pdflatex rather than
> > pdf-engine=path/to/pdflatex)
> > I have verified that I have the correct path to pdflatex.
> >
> > --
> > 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 [1][2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To post to this group, send email to
> > [2][3]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> > [3][4]https://groups.google.com/d/msgid/pandoc-discuss/
> d6542d6e-931b-4855-
> > 8673-4d0156d46121%[5]40googlegroups.com.
> > For more options, visit [4][6]https://groups.google.com/
> d/optout.
> >
> >References
> >
> > 1. mailto:[7]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > 2. mailto:[8]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > 3. [9]https://groups.google.com/d/msgid/pandoc-discuss/d6542d6e-
> 931b-4855-8673-4d0156d46121-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=
> email&utm_source=footer
> > 4. [10]https://groups.google.com/d/optout
>
> --
> 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 [11]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [12]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [13]https://groups.google.com/d/msgid/pandoc-discuss/e9a5dc66-97b7-4842
> -bc39-71f9f2a83682%40googlegroups.com.
> For more options, visit [14]https://groups.google.com/d/optout.
>
>References
>
> 1. http://file.md/
> 2. javascript:/
> 3. javascript:/
> 4. https://groups.google.com/d/msgid/pandoc-discuss/d6542d6e-931b-4855-
> 5. http://40googlegroups.com/
> 6. https://groups.google.com/d/optout
> 7. javascript:/
> 8. javascript:/
> 9. https://groups.google.com/d/msgid/pandoc-discuss/d6542d6e-931b-4855-8673-4d0156d46121-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 10. https://groups.google.com/d/optout
> 11. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 12. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 13. https://groups.google.com/d/msgid/pandoc-discuss/e9a5dc66-97b7-4842-bc39-71f9f2a83682-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 14. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-11-11 2:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 0:28 Kyle Eggleton
[not found] ` <d6542d6e-931b-4855-8673-4d0156d46121-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-11 2:30 ` Kyle Eggleton
2017-11-11 2:38 ` John MacFarlane
[not found] ` <20171111023832.GA16934-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2017-11-11 2:48 ` Kyle Eggleton
[not found] ` <e9a5dc66-97b7-4842-bc39-71f9f2a83682-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-11 2:58 ` John MacFarlane [this message]
[not found] ` <20171111025801.GE16934-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2017-11-11 3:14 ` Kyle Eggleton
[not found] ` <ac0af97c-47b8-4897-b61d-70f6c3ca6378-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-13 0:34 ` John MacFarlane
[not found] ` <20171113003454.GB81641-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-11-13 2:29 ` Kyle Eggleton
[not found] ` <d6d5710d-8e7e-477a-acef-062613ec460a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-04 23:44 ` Pedro Linares
[not found] ` <004aece5-4f06-4b58-9578-ef630cbe331d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-04 23:55 ` Pedro Linares
[not found] ` <511bcc1e-0537-46d0-a918-637bf2e769a7-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-05 1:38 ` John MACFARLANE
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=20171111025801.GE16934@MacBook-Air-2.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).