public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: denis.maier-NSENcxR/0n0@public.gmane.org,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: AW: custom writer with haskell
Date: Sat, 18 Dec 2021 11:45:38 -0800	[thread overview]
Message-ID: <m21r297l3x.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <4eb30ae54aea41cd9fdb2aa207f4b96e-NSENcxR/0n0@public.gmane.org>


<denis.maier-NSENcxR/0n0@public.gmane.org> writes:

> Does that have to be included? Can't one rely on Haskell being available? I mean, just like with Haskell filters....

By the time you've got your environment set up with ghc and all the
libraries installed properly, which you'd need to run interpreted
writers, you might as well just recompile pandoc with the revised
module.  I don't see a big advantage.


  parent reply	other threads:[~2021-12-18 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 14:05 denis.maier-NSENcxR/0n0
     [not found] ` <51f4c7e7b63344adb5967a8bfe3e50c8-NSENcxR/0n0@public.gmane.org>
2021-12-17 22:35   ` John MacFarlane
     [not found]     ` <yh480kfsqq2735.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-12-18 12:06       ` AW: " denis.maier-NSENcxR/0n0
     [not found]         ` <ee9cbe9414d947799907c62bce1408a8-NSENcxR/0n0@public.gmane.org>
2021-12-18 12:32           ` denis.maier-NSENcxR/0n0
     [not found]             ` <4eb30ae54aea41cd9fdb2aa207f4b96e-NSENcxR/0n0@public.gmane.org>
2021-12-18 19:45               ` John MacFarlane [this message]
     [not found]                 ` <m21r297l3x.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-21  8:51                   ` AW: " denis.maier-NSENcxR/0n0
     [not found]                     ` <c8f145c9d80f470f9adea4e3df82aab4-NSENcxR/0n0@public.gmane.org>
2021-12-21 14:18                       ` BPJ

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=m21r297l3x.fsf@Johns-Air.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=denis.maier-NSENcxR/0n0@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).