public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: state of the art in pandoc CLI wrappers?
Date: Wed, 18 May 2022 09:51:37 -0400	[thread overview]
Message-ID: <d7b0f530-f434-02f2-70fa-5eef2347d02d@reagle.org> (raw)

I have my own CLI wrapper and occasionally look in the state of things to see if I should use something mainstream. Looking at the [web page][1], I note three options:

[1]: https://pandoc.org/extras.html#cli-wrappers

1. pandocomatic, which still seems active
2. panrun hasn't been updated in years and doesn't respect
   underscore option (e.g., output_).
3. panzer is abandoned: "the --metadata-file option and Lua filters ...
   means that 90% of what can be done with panzer can be done with
   pandoc and some simple wrapper scripts. I no longer use panzer in my
   own workflow for this reason."

The panzer comment intrigued me because for my scripts I'm configuring specific CLI options, and metadata doesn't solve that, though providing templates/defaults could. Has anything else happened recently?

—Joseph

-- 
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/d7b0f530-f434-02f2-70fa-5eef2347d02d%40reagle.org.


             reply	other threads:[~2022-05-18 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 13:51 Joseph Reagle [this message]
     [not found] ` <d7b0f530-f434-02f2-70fa-5eef2347d02d-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-05-18 14:45   ` Albert Krewinkel
     [not found]     ` <87v8u2aoee.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-05-18 15:06       ` BPJ
2022-05-18 17:07       ` Joseph Reagle
     [not found]         ` <845cec37-32af-1a31-685a-dabc3d42b314-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2022-05-18 21:06           ` John MacFarlane
2022-05-18 21:13           ` Albert Krewinkel

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=d7b0f530-f434-02f2-70fa-5eef2347d02d@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).