From: Julien Dutant <julien.dutant-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: pandoc-select-code
Date: Wed, 22 Mar 2023 16:41:11 -0700 (PDT) [thread overview]
Message-ID: <e0f89eeb-15e4-432e-aec7-4dea9fb2adc2n@googlegroups.com> (raw)
In-Reply-To: <2b5ac86b6bac4345a332c34ab1547e7e-NSENcxR/0n0@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3287 bytes --]
Agreed! There's the wiki page
https://github.com/jgm/pandoc/wiki/Pandoc-Filters which seems to me a good
way of publicizing filters - Amy, you should list yours there! It doesn't
seem widely used though, not sure how many people know of it. It's not
listed in Pandoc Extras (because it's not a curated list?)
J
On Tuesday, March 21, 2023 at 8:59:54 AM UTC denis...-NSENcxR/0n0@public.gmane.org wrote:
> Thanks for letting us know about your new filters.
>
>
>
> In general, is there any chance such information could be collected
> somewhere? I feel I’m missing out on a lot of stuff if I just try to keep
> track of these interesting things myself. (I know there’s this page
> https://pandoc.org/extras.html) And we also have a repo for lua filters,
> but I’m not sure Amy’s filters are covered by these resources...)
>
>
>
> Best,
>
> Denis
>
>
>
> *Von:* pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> *Im
> Auftrag von *Amy de Buitléir
> *Gesendet:* Freitag, 17. März 2023 22:13
> *An:* pandoc-discuss <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
> *Betreff:* ANN: pandoc-select-code
>
>
>
> Announcing *pandoc-select-code*: a pandoc filter to extract only the code
> blocks. You might use this, for example, to extract sample code from a
> tutorial. This package has been available from my repo for a while, but I
> have now uploaded it to Hackage, and also made it available as a Nix flake.
>
> I originally developed this filter because I wanted something like
> literate Haskell, but using Markdown. I wanted to be able to write a
> Markdown file with Haskell code blocks, and then be able to compile and
> execute it, or use Pandoc to produce a PDF. Cabal doesn't support that, so
> one workaround is to pre-process the file using Pandoc with this filter and
> the --write=plain option to produce a source file that can be compiled.
>
> I also use this when I'm updating a tutorial I wrote some time ago; I'll
> extract the code examples and verify that they still work with the latest
> software.
>
> Hackage: https://hackage.haskell.org/package/pandoc-select-code
> Repo: https://github.com/mhwombat/pandoc-select-code
>
> --
> 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/40756e3f-ae25-4d1c-bfd5-6ec8321dd51dn%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/40756e3f-ae25-4d1c-bfd5-6ec8321dd51dn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/e0f89eeb-15e4-432e-aec7-4dea9fb2adc2n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 6368 bytes --]
prev parent reply other threads:[~2023-03-22 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHZWRUzJ0wOa3hY50CbcvoQO3tsY68E895g>
2023-03-17 21:12 ` ANN: pandoc-select-code Amy de Buitléir
[not found] ` <40756e3f-ae25-4d1c-bfd5-6ec8321dd51dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-21 8:59 ` AW: pandoc-select-code denis.maier-NSENcxR/0n0
[not found] ` <2b5ac86b6bac4345a332c34ab1547e7e-NSENcxR/0n0@public.gmane.org>
2023-03-22 23:41 ` Julien Dutant [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=e0f89eeb-15e4-432e-aec7-4dea9fb2adc2n@googlegroups.com \
--to=julien.dutant-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).