public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc on cygwin's shell
Date: Sun, 23 Jul 2017 09:39:30 +0200	[thread overview]
Message-ID: <20170723073929.GA67976@macbook-air-2.home> (raw)
In-Reply-To: <11f3d0c4-d3d1-4ec5-ba5f-c4fe6e05e052-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

findExecutable from System.Directory is being used to check
for the existence of the program and issue and error if it's
not found.

The docs for findExecutable say:

> On Windows, findExecutable calls the Win32 function
> SearchPath, which may search other places before checking
> the directories in the PATH environment variable. Where it
> actually searches depends on registry settings, but
> notably includes the directory containing the current
> executable.

So that might be a clue about what's happening.

We could try removing that check and just letting things
fail at the point where we try to run the tex program.
But the check is nice because we can give a more informative
message early on.

+++ Luis Rivera [Jul 22 17 11:40 ]:
>   Hello!
>   I uncluttered my hard drive and kept TeXLive on Cygwin. Tested if the
>   [pdf|lua|xe]LaTeX engines worked, and there I go trying to make a nice
>   pdf with pandoc inside cygwin's bash. Alas, the pandoc windows binary
>   looks for windows executables, and afaics these engines run as
>   softlinks, not exes, in cygwin, the real executables being
>   [pdf|lua|xe]tex. Is there any workaround known to run windows pandoc
>   inside the shell in cygwin?
>   Thanks in advance,
>
>   --
>   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]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/11f3d0c4-d3d1-4ec5-
>   ba5f-c4fe6e05e052%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/11f3d0c4-d3d1-4ec5-ba5f-c4fe6e05e052-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-07-23  7:39 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 [this message]
     [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
     [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=20170723073929.GA67976@macbook-air-2.home \
    --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).