public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Lua filters: Extensions with pandoc.read?
Date: Tue, 4 Oct 2022 10:25:51 -0700	[thread overview]
Message-ID: <5AC38771-6A87-47C2-80C7-5C7B389EDD1B@gmail.com> (raw)
In-Reply-To: <87r0zn3dff.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>



> On Oct 4, 2022, at 6:31 AM, Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> wrote:
> 
> Mmmh, good point. My initial idea was to use the format's default
> extension when no `extensions` field is given. But that's confusing,
> because now omitting the `extensions` field can have multiple meanings
> ("fall back to reader options" or "use default extensions"), depending
> on which other fields are set. Not a good interface.


Not sure about this, but what about?

- if no `extensions` field is present, then default extensions for that format are used, as possibly modified by `+` or `-` in the format specifier
- if `extensions` is present, then those extensions will be used, instead of the defaults; if you want no extensions, just use `ejxtensions = {}`
- if `extensions` is present *and* modifiers to format, then start with `extensions` and apply the modifiers


  parent reply	other threads:[~2022-10-04 17:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 12:02 BPJ
     [not found] ` <CADAJKhCqSXXZBPvXRfr+h4ady_yCzO6s=VDKY_Tt54dcLtDR5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-19 12:39   ` Albert Krewinkel
     [not found]     ` <87czbrfrzr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-09-19 13:34       ` BPJ
     [not found]         ` <CADAJKhApJjnCMghJ61rg6H2U9_zOP3Q=RJxHc9E2dFUH0Py+Sg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-04  9:13           ` Albert Krewinkel
     [not found]             ` <87v8oz3ohm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-10-04 10:33               ` BPJ
     [not found]                 ` <CADAJKhCg3rMk+0fJBOcte32BVh2c9tYQHa57DEGHdyAz2u7+kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-04 13:31                   ` Albert Krewinkel
     [not found]                     ` <87r0zn3dff.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-10-04 17:25                       ` John MacFarlane [this message]
     [not found]                         ` <5AC38771-6A87-47C2-80C7-5C7B389EDD1B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-06 11:11                           ` BPJ
     [not found]                             ` <CADAJKhCan6ec3ruV5r08ynTFPVLUtOpc=h+Jt7-geYNUcJb6QA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-07  6:16                               ` 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=5AC38771-6A87-47C2-80C7-5C7B389EDD1B@gmail.com \
    --to=fiddlosopher-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).