From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'K' via pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pdf-engine pdflatex not known - windows, miktex portable
Date: Thu, 4 Jan 2018 08:27:11 -0800 [thread overview]
Message-ID: <20180104162711.GD15709@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I'm not sure why there'd be a difference btw pandoc 1 and 2.
I've looked at the code and nothing is jumping out at me.
+++ 'K' via pandoc-discuss [Jan 03 18 23:29 ]:
> Thanks for your response.
> Because of using it in a batch-file I could temporary change the
> path-variable without a problem and after that it runs smoothly.
> Is pandoc 2 searching for ( / needing) supporting-files from miktex /
> pdflatex? (and version 1.x doesn't do that?)
> But that workaround is good enough for me.
> Thanks for your quick help.
> Am Mittwoch, 3. Januar 2018 19:42:23 UTC+1 schrieb John MacFarlane:
>
> Generally this would happen if the program is not found
> when pandoc tries to run the process. I'm not sure why that
> would be.
> Try just using --pdf-engine=pdflatex and putting the
> relevant directory in your path (perhaps temporarily).
> +++ 'K' via pandoc-discuss [Jan 03 18 04:03 ]:
> > Hi,
> > I'm using portable Versions of pandoc and miktex on a Windows
> System.
> > With pandoc 1.19.2.1 converting a markdown-File to PDF runs fine
> - the
> > used commandline looks like this:
> > D:\pandoc\pandoc_1.19.2.1\pandoc.exe -o docs\file.pdf
> > --latex-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc
> > docs\[1]file.md
> > After upgrading pandoc to 2.0.6 I have to change the parameter
> > --latex-engine to --pdf-engine. The new commandline that would
> be used
> > was this:
> > D:\pandoc\pandoc_2.0.6\pandoc.exe -o docs\file.pdf
> > --pdf-engine=D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe --toc
> > docs\[2]file.md
> > Following is the response I get:
> > pdf-engine D:\LaTeX\MiKTeX_2.9\miktex\bin\pdflatex.exe not known
> > I have updated Miktex, but the result is the same. With 1.19.2.1
> the
> > PDF will be created.
> > Thanks for any helpfull advice.
> > Greetings
> > Karsten
> >
>
> --
> 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 [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [4]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [5]https://groups.google.com/d/msgid/pandoc-discuss/0fa916f1-8d06-41ca-
> 9d2a-18ca616c37f2%40googlegroups.com.
> For more options, visit [6]https://groups.google.com/d/optout.
>
>References
>
> 1. http://file.md/
> 2. http://file.md/
> 3. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 4. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 5. https://groups.google.com/d/msgid/pandoc-discuss/0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 6. https://groups.google.com/d/optout
next prev parent reply other threads:[~2018-01-04 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 12:03 'K' via pandoc-discuss
[not found] ` <54e1c2fd-4777-4f44-b956-0dcc73c2b832-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-03 18:42 ` John MACFARLANE
2018-01-04 7:29 ` 'K' via pandoc-discuss
[not found] ` <0fa916f1-8d06-41ca-9d2a-18ca616c37f2-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-04 16:27 ` John MacFarlane [this message]
[not found] ` <20180104162711.GD15709-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2018-01-05 7:57 ` 'K' via pandoc-discuss
[not found] ` <47a53a1e-9098-459f-b88f-618c6ded03e4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-06-20 7:56 ` Giacomo Lanza
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=20180104162711.GD15709@Johns-MacBook-Pro.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).