public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Amy de Buitléir" <amy-x92Y4IBCQKU6Cx7ujrKbww@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: ANN: pandoc-select-code
Date: Fri, 17 Mar 2023 14:12:31 -0700 (PDT)	[thread overview]
Message-ID: <40756e3f-ae25-4d1c-bfd5-6ec8321dd51dn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]

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-discuss+unsubscribe-/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.

[-- Attachment #1.2: Type: text/html, Size: 1779 bytes --]

             reply	other threads:[~2023-03-17 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHZWRUzJ0wOa3hY50CbcvoQO3tsY68E895g>
2023-03-17 21:12 ` Amy de Buitléir [this message]
     [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         ` pandoc-select-code Julien Dutant

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=40756e3f-ae25-4d1c-bfd5-6ec8321dd51dn@googlegroups.com \
    --to=amy-x92y4ibcqku6cx7ujrkbww@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).