From: Florian Cramer <flrncrmr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc on cygwin's shell
Date: Tue, 5 Jun 2018 03:31:43 -0700 (PDT) [thread overview]
Message-ID: <23ae3775-6081-41ed-821f-965a87b8450c@googlegroups.com> (raw)
In-Reply-To: <730d6fe9-cef2-4839-8090-c28ea609375a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2246 bytes --]
Thanks a lot, Luis, for this workaround!
However, I still have trouble getting it work. My steps are the following:
1) Create a shell (wrapper) script that invokes pdfroff (respectively any
other needed executable):
#!/bin/sh
/cygdrive/c/cygwin64/bin/pdfroff $*
Then compile this script into a Windows executable with shc:
shc -f pdfroff.sh
...rename the resulting executable pdfroff.sh.x to pdfroff.exe and move it
into a directory inside c:\ProgramFiles . (I also tried /usr/local/bin and
the current working directory.)
However, this is still doesn't work with pandoc; I still get the error
message "pdfroff not found. Please select a different --pdf-engine or
install pdfroff"
On Friday, May 25, 2018 at 6:17:07 PM UTC+2, Luis Rivera wrote:
>
>
>
> On Friday, 25 May 2018 06:16:36 UTC-5, Florian Cramer wrote:
>>
>> Is there some practical fix for this issue in the meantime? Linking the
>> Cygwin tex binaries into a Windows system directory or something similar?
>>
>> I've been struggling with this issue for quite a long time... (It also
>> occurs when you try to use pdfroff as a backend for the PDF writer, with
>> pdfroff being installed in Cygwin.)
>>
>>
> pdfroff is a shell program; so what I've done is to compile it into an
> executable with Javier Rosales's shell compiler [shc](
> http://www.datsi.fi.upm.es/~frosal/) and make pandoc happy: it checks for
> and executable, it finds it, and then runs it. I've done the same for the
> TeX family: originally, they are symiinks, so I wrapped the calls to each
> of them (pdflatex, xelatex, lualatex) into shell programs and compiled
> aliases accordingly.
>
> Hope that helps,
>
>
--
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/23ae3775-6081-41ed-821f-965a87b8450c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 5322 bytes --]
next prev parent reply other threads:[~2018-06-05 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 18:40 Luis Rivera
[not found] ` <11f3d0c4-d3d1-4ec5-ba5f-c4fe6e05e052-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-23 7:39 ` John MacFarlane
[not found] ` <20170723073929.GA67976-gd5emFPDCk1l5R22fHXGm0EMvNT87kid@public.gmane.org>
2017-07-24 20:51 ` Luis Rivera
2017-07-26 2:44 ` Luis Rivera
[not found] ` <e44f1c65-26b3-4f6a-aa63-f494a48f8245-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-26 7:11 ` John MacFarlane
[not found] ` <20170726071135.GA15440-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2018-05-25 11:16 ` Florian Cramer
[not found] ` <794616e3-f260-4656-b90a-563b820d5db1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-05-25 16:17 ` Luis Rivera
[not found] ` <730d6fe9-cef2-4839-8090-c28ea609375a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-06-05 10:31 ` Florian Cramer [this message]
[not found] ` <23ae3775-6081-41ed-821f-965a87b8450c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-06-05 21:27 ` Luis Rivera
2018-05-27 17:02 ` Mikolaj Machowski
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=23ae3775-6081-41ed-821f-965a87b8450c@googlegroups.com \
--to=flrncrmr-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).