From: Mikolaj Machowski <mikmach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc on cygwin's shell
Date: Sun, 27 May 2018 10:02:01 -0700 (PDT) [thread overview]
Message-ID: <dea35415-a0b1-49dd-8922-5344baa2bca7@googlegroups.com> (raw)
In-Reply-To: <20170723073929.GA67976-gd5emFPDCk1l5R22fHXGm0EMvNT87kid@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1135 bytes --]
On Sunday, July 23, 2017 at 9:39:47 AM UTC+2, John MacFarlane wrote:
>
>
> 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.
>
I am also using Windows pandoc in cygwin and cannot use tex/pdf export.
If current solution has specific merits maybe it would be better not to
change it but add another pdfengine (or switch/option) which would skip
this check?
--
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/dea35415-a0b1-49dd-8922-5344baa2bca7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1742 bytes --]
prev parent reply other threads:[~2018-05-27 17:02 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
[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 [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=dea35415-a0b1-49dd-8922-5344baa2bca7@googlegroups.com \
--to=mikmach-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).