From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Denis Maier
<denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Haskell filters documentation
Date: Tue, 01 Sep 2020 09:11:52 -0700 [thread overview]
Message-ID: <m2mu29v5mf.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <98400308-c788-7626-7cfe-ce24d42bcfca-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
Feel free to ask questions here. The docs are written by people
who have been Haskellers a long time and may have forgotten what
is obvious and what is not!
Denis Maier <denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org> writes:
> Hi
> I've started learning some Haskell, and, as going through tutorials and
> textbooks feels a bit dull, I thought dabbling with a Pandoc filter
> could be a nice (and hopefully useful) exercise. Just: I have to admit I
> feel totally lost, and the documentation seems to assume much more
> Haskell knowledge than I currently have. The types documentation is
> rather technical. Have I overlooked something? Any hints or advice on
> how to get started are highly appreciated.
> Best,
> Denis
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/98400308-c788-7626-7cfe-ce24d42bcfca%40mailbox.org.
prev parent reply other threads:[~2020-09-01 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 7:35 Denis Maier
[not found] ` <98400308-c788-7626-7cfe-ce24d42bcfca-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-01 9:27 ` Albert Krewinkel
2020-09-01 16:11 ` John MacFarlane [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=m2mu29v5mf.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=denis.maier.lists-cl+VPiYnx/1AfugRpC6u6w@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).